Agent Readiness Auditor
NPM · AGENT-READINESS-AUDITOR
Audits any website for AI agent readiness and safety, scoring prompt injection risk and llms.txt.
Available components
Last scanned (5 hours ago)
Scores higher than 98% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 114 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to asish-singh/agent-readiness-auditor). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 144 tokens (~144/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +45
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.90 ▲ functional
- Package version: 0.4.7 → 0.5.0 functional
- 12 Oct 26 −44
- Stability: 0.80 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.4.7 → 0.5.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/agent-readiness-auditor@0.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | asish-singh/agent-readiness-auditor |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/asish-singh/agent-readiness-auditor/.github/workflows/release.yml@refs/tags/v0.5.0 |
| Rekor log index | 3213267817 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bba1d2f566c0b705e17bf69a01880307b6e871ec854bcdf992f17a75730b1d1b78e03730d5c28dfe46928c378e8ed4bc3f8795edb08feb0d887c547ae |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Deprecated | 1 |
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_site Audit a website for AI agent readiness ~144
Fetches a website (crawling multiple pages) and scores how well it works with, and defends against, AI agents. Runs nine checks: hidden prompt injection text, llms.txt, the robots.txt stance on AI crawlers, structured data, accountability links, sitemap, content structured for AI answers, accidental index blocking, and whether an agent endpoint is advertised, including a /.well-known/ai-catalog.json listing MCP server cards. Returns a score out of 100, a letter grade, and a finding for each check with a suggested fix.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to audit, as a bare domain (example.com) or full URL |
No output schema declared.
No examples provided.
How do I install the Agent Readiness Auditor MCP server?
Agent Readiness Auditor runs locally as an npm package, launched with npx -y agent-readiness-auditor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agent-readiness-auditor
claude mcp add asish-singh-agent-readiness-auditor -- npx -y agent-readiness-auditor
What is the Agent Readiness Auditor MCP server?
Agent Readiness Auditor is an MCP server listed in the public MCP registry as io.github.asish-singh/agent-readiness-auditor. Audits any website for AI agent readiness and safety, scoring prompt injection risk and llms.txt. This page covers its npm package (agent-readiness-auditor).
Is the Agent Readiness Auditor MCP server safe to use?
Agent Readiness Auditor scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Readiness Auditor MCP server expose?
Agent Readiness Auditor exposes 1 tool: audit_site. Their descriptions and schemas cost roughly 144 tokens of context every time the server is loaded.
Is the Agent Readiness Auditor MCP server still maintained?
Agent Readiness Auditor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Agent Readiness Auditor MCP server under?
Agent Readiness Auditor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.