Skip to main content
Glama
Sign In
SiteLint Auditor MCP

SiteLint Auditor MCP

Official
by sitelint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to SiteLint Auditor MCP

No user-submitted related servers found.

    Related Servers

    • sage-audit

      tmolavi
      A
      license
      Not graded
      quality
      B
      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

    • agentic-seo-check

      rivi-software
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to audit URLs, static build output, raw HTML, and whole sites for SEO issues, returning actionable findings with rule IDs, severities, fixes, selectors, and evidence, plus optional JavaScript rendering and Lighthouse performance checks.
      2,197 npm
      2
      MIT

    • SiteProbe MCP Server

      tmolavi
      A
      license
      Not graded
      quality
      B
      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.
      6
      MIT

    • mcp-seo

      g-battaglia
      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

    • mcp-a11y-tools

      rog0x
      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.
      46 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 recent community issues

    Resources