Skip to main content
Glama
sitelint
by sitelint

Related Servers

Alternatives to SiteLint Auditor MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to audit URLs or raw HTML for SEO, AEO, and GEO performance, generate llms.txt manifests, and check the tool version via MCP tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes website auditing, finding retrieval, and safe fix application as MCP tools so AI agents can diagnose and remediate SEO, accessibility, and technical web issues.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to perform comprehensive SEO audits on web pages, including meta tags, headings, links, images, performance, and more, via a CLI or MCP server.
      18
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with web accessibility analysis tools via MCP, enabling checks for alt text, heading hierarchy, color contrast, ARIA validation, and form accessibility.
      11 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform real accessibility audits by controlling a browser, running axe-core scans, reviewing page structure, images, tab order, and WCAG 2.2 color contrast, all over MCP with local session logging.
      21
      23 npm
      1
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Core issue tools list_issues/get_issue are clearly distinct retrieval levels, and audit_html/audit_url separate raw markup from live URL auditing. However, check_wcag_criterion overlaps heavily with audit_url's optional success-criteria filtering, and capture_page_issues vs audit_url both load pages, so an agent could sometimes hesitate between them.

    Naming Consistency5/5

    All names use snake_case and a predictable verb_noun pattern: list_issues, get_issue, capture_page_issues, audit_html, audit_url, check_wcag_criterion. Singular/plural differences (get_issue vs list_issues) follow normal REST-like conventions.

    Tool Count5/5

    Six tools is well-scoped for an auditing server, with each tool covering a distinct operation: retrieve issues, inspect issue detail, capture runtime issues, audit HTML, audit URL, and check one WCAG criterion. No obvious filler or missing bulk.

    Completeness4/5

    The surface covers issue discovery/detail, live page capture, HTML/URL audits, and single-criterion checks, which are the core operations for an auditor. Minor gaps exist around batch/multi-page auditing or listing available sites/audit history, but these are likely workable around.

    Maintenance

    ActivityActive
    ResponsivenessNo issues