Skip to main content
Glama
Vinizeira13

interface-audit-mcp

by Vinizeira13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to interface-audit-mcp

No user-submitted related servers found.

    Related Servers

    • a11y-mcp-server

      aiuxmasters
      A
      license
      A
      quality
      C
      maintenance
      Exposes axe-core accessibility auditing as MCP tools so any MCP-compatible agent can audit HTML for structural and semantic issues.
      3
      MIT

    • polish

      tomiabe
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted design audit MCP server that reviews UI code against Nielsen's heuristics and an accessibility rubric, returning scores and fixable findings. It also enables verifying previously flagged issues against updated code.
      60 npm
      BSD 4-Clause "Original" or "Old"

    • Product Page Audit

      SvenKunkka
      A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that lets AI assistants run audits of generic HTML and Shopify product pages, gathering reproducible evidence on identity, structured data, images, links, specifications, and optional browser or link checks. It returns JSON and Markdown reports that the client can interpret, while keeping automated findings separate from checks requiring human judgment.
      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

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one performs an audit of HTML content, the other lists the rule catalog. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: 'audit_html' and 'list_rules'. The naming is clear, predictable, and adheres to a uniform style.

    Tool Count5/5

    With only two tools, the server is tightly focused on its core functionality of auditing and providing rule information. This count is appropriate and avoids unnecessary bloat.

    Completeness4/5

    The server covers the primary audit and rule-listing needs. However, it might benefit from additional tools such as retrieving specific audit results or configuration, but the current set is sufficient for a minimal viable interface-audit server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources