io.github.forgemeshlabs/agent-readiness-mcp
NPM · @FORGEMESHLABS/AGENT-READINESS-MCP · SCANNED SEP 23
Agent Readiness MCP — the free Agent Readiness scanner as an MCP server. Measures your ASO Score.
Available components
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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 800 tokens (~160/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the io.github.forgemeshlabs/agent-readiness-mcp server?
io.github.forgemeshlabs/agent-readiness-mcp runs locally as an npm package, launched with npx -y @forgemeshlabs/agent-readiness-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @forgemeshlabs/agent-readiness-mcp
claude mcp add forgemeshlabs-agent-readiness-mcp -- npx -y @forgemeshlabs/agent-readiness-mcp
{
"mcpServers": {
"forgemeshlabs-agent-readiness-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/agent-readiness-mcp"
]
}
}
} {
"servers": {
"forgemeshlabs-agent-readiness-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/agent-readiness-mcp"
]
}
}
} codex mcp add forgemeshlabs-agent-readiness-mcp -- npx -y @forgemeshlabs/agent-readiness-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"forgemeshlabs-agent-readiness-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@forgemeshlabs/agent-readiness-mcp"
],
"enabled": true
}
}
} openclaw mcp add forgemeshlabs-agent-readiness-mcp --command npx --arg -y --arg @forgemeshlabs/agent-readiness-mcp
mcp_servers:
forgemeshlabs-agent-readiness-mcp:
command: "npx"
args: ["-y", "@forgemeshlabs/agent-readiness-mcp"] {
"McpServers": {
"forgemeshlabs-agent-readiness-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@forgemeshlabs/agent-readiness-mcp"
]
}
}
} assistant mcp add forgemeshlabs-agent-readiness-mcp -t stdio -c npx -a -y @forgemeshlabs/agent-readiness-mcp
{
"mcpServers": {
"forgemeshlabs-agent-readiness-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/agent-readiness-mcp"
]
}
}
} 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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +3
- Stability: unverified → 0.27 ▲ 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 23 Sept 2026 · Analysed npm/@forgemeshlabs/agent-readiness-mcp@0.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
check_signal Run a single agent-readiness check ~175
Run one specific agent-readiness check against a site (e.g. 'a2a-agent-card', 'llms-txt', 'mcp-server-card', 'x402'). Use this for targeted validation after making a fix or when debugging one signal; use scan_site for the complete ASO Score and get_fix_plan for a prioritized remediation roadmap. Use list_checks first when you need valid check ids. Returns status, evidence, and a fix recommendation, and omits raw remote artifacts by default.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | Lowercase check slug from list_checks, e.g. 'a2a-agent-card', 'llms-txt', 'mcp-server-card', or 'x402'. |
| url | string | yes | Website URL or domain to scan, e.g. https://example.com or example.com |
No output schema declared.
No examples provided.
get_aso_framework ASO framework reference ~88
Return the ASO (Agent Signal Optimization) framework reference: the six signal pillars with point weights, the Agent Readiness Index maturity levels (ASO-0 through ASO-5), certification thresholds, and the scoring rubric. Use this for education, documentation, or explaining how scores are calculated; it does not fetch or scan a website. Source: https://agentsignaloptimization.com
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fix_plan Get a prioritized ASO fix plan ~132
Scan a site and return a prioritized remediation plan: which signals to add first, the ASO Score points each fix is worth, and ready-to-paste artifact templates (robots.txt AI rules, llms.txt, agent.json, A2A agent-card.json, MCP server card, x402 manifest, pricing.json, security.txt, status endpoint). Use this when the user wants an implementation roadmap or copy-paste fixes; use scan_site when they need full evidence and per-check scoring, and use check_signal to verify one completed fix.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL or domain to plan fixes for |
No output schema declared.
No examples provided.
list_checks List all agent-readiness checks ~64
List the full catalog of supported ASO checks with id, name, category, description, and spec link. Use this before check_signal to discover valid check ids, to build UI filters, or to explain the scanner coverage; it does not scan a site or produce a score.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_site ASO Scan — measure your ASO Score ~341
Scan a website for Agent Readiness using the ASO (Agent Signal Optimization) framework and return an Agent Readiness Report. Use this for a full site-level baseline, competitive audit, or before/after readiness measurement; use check_signal instead when you only need one named signal, and use get_fix_plan when you only need remediation steps. Runs 34 checks across discoverability (robots.txt, sitemap, llms.txt, DNS-AID, Link headers), content accessibility (markdown negotiation), bot access control (AI bot rules, Content Signals, Web Bot Auth), invocation (API catalog, OAuth discovery, OAuth protected resource, auth.md, MCP Server Card, Google A2A Agent Card, Agent Skills, WebMCP), commerce (x402, MPP, UCP, ACP, pricing), Google generative AI search basics, browser-agent UX, and identity/trust signals. Returns the ASO Score (0-100, formally the Agent Readiness Index), ASO maturity level (ASO-0 Invisible … ASO-5 Autonomous-Commerce-Ready), an agent-readiness verdict, per-pillar scores, per-check evidence, and prioritized recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional category filter for focused scans. Omit for all 34 checks; pass one or more category enum values to narrow runtime and output. |
| include_artifacts | boolean | – | Optional raw artifact return. Default false. When true, includes remote manifests such as agent.json and A2A cards as untrusted attacker-controlled data for debugging only. |
| url | string | yes | Website URL or domain to scan, e.g. https://example.com or example.com |
No output schema declared.
No examples provided.
What is the io.github.forgemeshlabs/agent-readiness-mcp server?
io.github.forgemeshlabs/agent-readiness-mcp is listed in the public MCP registry as io.github.forgemeshlabs/agent-readiness-mcp. Agent Readiness MCP, the free Agent Readiness scanner as an MCP server. Measures your ASO Score. This page covers its npm package (@forgemeshlabs/agent-readiness-mcp).
Is the io.github.forgemeshlabs/agent-readiness-mcp server safe to use?
io.github.forgemeshlabs/agent-readiness-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. 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 io.github.forgemeshlabs/agent-readiness-mcp server expose?
io.github.forgemeshlabs/agent-readiness-mcp exposes 5 tools: scan_site, check_signal, list_checks, get_fix_plan, get_aso_framework. Their descriptions and schemas cost roughly 800 tokens of context every time the server is loaded.
Is the io.github.forgemeshlabs/agent-readiness-mcp server still maintained?
io.github.forgemeshlabs/agent-readiness-mcp is still listed as active in the MCP registry. We last reached this channel on 23 September 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 io.github.forgemeshlabs/agent-readiness-mcp server under?
io.github.forgemeshlabs/agent-readiness-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.