mcpdirectory.dev
9,129 servers · updated 23 Sept

Agent Accessibility Auditor MCP server

community Active last commit 21 d
{
  "mcpServers": {
    "mambabuilt-agent-accessibility-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-agent-accessibility-auditor@latest"
      ],
      "env": {
        "APIFY_TOKEN": "<apify_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @mambalabsdev/mcp-agent-accessibility-auditorversion 1.1.0

What it does

This server audits whether AI agents and crawlers can access a website by checking for llms.txt, robots.txt AI directives, structured data, and machine-readable endpoints. It returns 42 fields across five categories of site accessibility data for developers and SEO engineers preparing sites for AI traffic.

  • Check if a domain has llms.txt and robots.txt AI crawler policies before deploying a site for AI agent access.
  • Audit a list of client domains to see which ones support structured data, sitemaps, and other machine-readable formats.
  • Compare before-and-after snapshots of a website's agent accessibility after implementing llms.txt or updating robots.txt directives.

Tools this server exposes

ToolDoes
audit_agent_accessibilityAudits a domain and returns whether AI agents can read it, checking for llms.txt, robots.txt AI policy, structured data, sitemaps, OpenAPI specs, security.txt,

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.