Agent Accessibility Auditor MCP Server
Agent Accessibility Auditor MCP Server
MCP server for the Mamba Labs Agent Accessibility Auditor actor on Apify.
Can an AI agent read this site? Give it a domain and it returns one flat row of 42 fields covering five families of fact: the llms.txt family, robots AI crawler policy including the newer Content Signal directives, structured data presence and health, render mode, and machine readable endpoint discovery.
Install
npx -y @mambalabsdev/mcp-agent-accessibility-auditorClaude Desktop
{
"mcpServers": {
"mamba-agent-accessibility-auditor": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-agent-accessibility-auditor"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get an Apify token at console.apify.com/account/integrations.
Tool
audit_agent_accessibility
Domain in, whether an AI agent can read that site out.
Input | Type | Required | Notes |
| string | yes | One company domain, for example vercel.com. Protocol and path are stripped. |
| array | no | Run only these checks: |
| boolean | no | Alias for the checks array: false removes |
| boolean | no | Alias for the checks array: false removes |
| enum | no | Leave as |
Reading the output
Every field is a fact read off a fetch. No model is called at any point, so the same domain returns the same row today and next month unless the site actually changed.
has_llms_txt is true only when /llms.txt returns 200 and the body is real markdown, and llms_txt_reject_reason says why a 200 was not counted. Twelve requests per domain, robots.txt first and then the homepage and ten probes concurrently. Typical wall clock is 2 to 4 seconds.
Built for a technical SEO or growth engineer preparing a site for AI crawlers and agent traffic, or an agency selling that work and needing a before and after audit across a client list.
Billing
You are charged per domain analyzed, plus a small actor start fee. A repeat run inside the 7 day cache window costs nothing new.
Pricing is on the actor's Apify page. Running this server consumes Apify credits.
What this server does and does not do
It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.
Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.
Source
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-agent-accessibility-auditor'
If you have feedback or need assistance with the MCP directory API, please join our Discord server