aso-audit-mcp
This server scans websites for AI-agent readiness and returns ASO (Agent Signal Optimization) scores, detailed check evidence, and prioritized fix plans.
scan_site — Run a full ASO scan: get an Agent Readiness Report with ASO Score, maturity level (ASO-0 to ASO-5), per-pillar breakdowns, all 34 check results, evidence, and recommendations. Optionally limit by category or include raw parsed manifests.
check_signal — Run a single agent-readiness check (e.g.
a2a-agent-card,llms-txt,mcp-server-card,x402) to get status, evidence, and a fix recommendation.list_checks — List the full catalog of checks the scanner runs, including ids, names, categories, descriptions, and spec links.
get_fix_plan — Scan a site and get a prioritized remediation plan with ASO point values and ready-to-paste templates (robots.txt AI rules, llms.txt, agent.json, A2A card, MCP server card, x402 manifest, pricing.json, security.txt, status endpoint).
get_aso_framework — Retrieve the ASO framework reference: the six signal pillars with weights, maturity levels, certification thresholds, and scoring rubric.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@aso-audit-mcp Scan example.com for agent readiness report"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
aso-mcp — the free Agent Readiness Scanner
What's your ASO score?
SEO made you visible to search engines. ASO (Agent Signal Optimization) makes you discoverable, trustable, and payable by the AI agents that are becoming the web's next visitors.
aso-mcp is the free, open-source ASO Scanner — an MCP server that scans any website and produces an Agent Readiness Report scored on the open ASO framework. The beta npm package is @forgemeshlabs/aso-audit-mcp.
This release tracks Google's current agent-readiness guidance without overstating it: Google Search says traditional SEO fundamentals still apply to generative AI search, llms.txt is ignored by Google Search itself, and browser agents benefit from clean DOM, screenshot, and accessibility-tree signals. The scanner keeps llms.txt because non-Google agents use it, and adds a browser-agent UX check for semantic controls, linked labels, ARIA/role fallbacks, and hidden-overlay risk.
Beta. Experimental ASO scanner for evaluating whether agents can discover, trust, understand, and use a website/API/tool. ASO scoring is experimental and will evolve as agent standards mature.
=== Agent Readiness Report: https://example.com ===
ASO Score: 70/100
Agent Readiness: Ready
Level: ASO-4 Trustable — Agents can verify trust, reputation, and operational signals.
Discoverability 20/20 Identity 15/20 Trust 11/15
Commerce 5/15 Reputation 4/15 Memory 15/15What it checks — 34 signals across 6 pillars
Find gaps in discovery, trust, interoperability, and commerce — every emerging agent standard in one scan:
Pillar / Category | Checks |
Discovery | robots.txt, sitemap.xml, Link headers, DNS-AID ( |
Content | Markdown content negotiation, llms.txt, LLM-readable docs ( |
Bot Access | Explicit AI crawler rules (GPTBot, ClaudeBot, Google-Extended, PerplexityBot…), Content Signals, Web Bot Auth |
Interoperability | API Catalog (RFC 9727), OAuth discovery (RFC 8414), OAuth Protected Resource (RFC 9728), auth.md, MCP Server Card ( |
Commerce | x402, MPP, UCP, ACP, machine-readable pricing |
Identity & Trust | HTTPS enforcement, JSON-LD/schema.org, agent-friendly browser UX, OpenAPI, agent.json, security.txt, status endpoint, versioning, cross-file identity & signal consistency |
Related MCP server: ASO Score MCP
Deterministic x402 v2 endpoint audit
The MCP tool audit_x402_endpoint complements the origin-wide ASO scan with a
no-spend protocol audit of one paid endpoint. It returns a 0-100 score, A-F
grade, compliance verdict, per-check booleans, failed checks, and observed
schemes/networks/extensions. It validates the live 402 challenge but never
sends PAYMENT-SIGNATURE, so it cannot authorize or settle a payment.
Checks: HTTPS/TLS, HTTP 402, PAYMENT-REQUIRED, Base64 JSON, x402Version: 2,
non-empty accepts, CAIP-2 networks, required payment fields, and JSON content
type. For body-gated routes, pass method, body, and optionally
content_type.
This is deliberately reported separately from the ASO Score: protocol compliance does not prove discoverability, trust, settlement, idempotency, or paid-response quality.
Living standards model
Agent protocols are changing quickly. The scanner is maintained as part of a living framework: checks are versioned, and stable standards, optional capabilities, release candidates, drafts, and vendor conventions are labeled separately. See the dated scanner source list and the canonical ASO source registry.
Every check returns pass / partial / fail with concrete evidence and a fix recommendation. Results roll up into the six ASO pillars (Discoverability 20, Identity 20, Trust 15, Commerce 15, Reputation 15, Memory 15) → your ASO Score and maturity level.
Install
Requires Node.js ≥ 20. Published on npm as @forgemeshlabs/aso-audit-mcp — no clone or build needed.
npm install -g @forgemeshlabs/aso-audit-mcpOr skip the install entirely and run it with npx (recommended for MCP clients):
npx -y @forgemeshlabs/aso-audit-mcpClaude Code
claude mcp add aso -- npx -y @forgemeshlabs/aso-audit-mcpClaude Desktop / Cursor / Windsurf (any MCP client)
{
"mcpServers": {
"aso": {
"command": "npx",
"args": ["-y", "@forgemeshlabs/aso-audit-mcp"]
}
}
}Development (from source)
Only needed if you're hacking on the scanner itself:
git clone https://github.com/forgemeshlabs/aso-audit-mcp
cd aso-audit-mcp
npm install && npm run build
claude mcp add aso -- node /path/to/aso-audit-mcp/dist/index.jsTools
Tool | What it does |
| Free menu: every tool below with its price (all $0) — for agents that pick before calling |
| Full ASO scan → Agent Readiness Report: ASO Score, level, pillar breakdown, all 34 checks with evidence + recommendations |
| Prioritized remediation plan with ready-to-paste templates (robots.txt AI rules, llms.txt, agent.json, A2A agent card, MCP server card, x402 manifest, pricing.json, security.txt, status endpoint) |
| Run one specific check (e.g. |
| Catalog of every check with spec links |
| The ASO rubric: pillars, weights, levels, certification thresholds |
Try it: "Scan example.com for agent readiness" · "What's my ASO score?" · "Give me a fix plan to make my site agent-ready."
CLI smoke test (from a source checkout)
npm run smoke -- https://your-site.comGlama / registry metadata
This repository includes glama.json for Glama MCP registry ownership and install metadata.
Package:
@forgemeshlabs/aso-audit-mcpCurrent release:
v0.4.4Transport: local
stdioAuthentication: none required for local
stdiouse. The scanner does not ask for API keys, tokens, cookies, or third-party credentials.HTTP deployment: not enabled by this npm package. Any public HTTP deployment of this scanner must add authentication, per-client rate limits, request logging, and an egress policy before exposure.
Recommended Glama/MCP install command:
npx -y @forgemeshlabs/aso-audit-mcpExample usage after connecting the server to an MCP client:
Scan https://example.com for agent readiness.
Give me the ASO fix plan for example.com.
Check only the llms-txt signal for example.com.
List the ASO scanner checks.Release verification:
Git tag:
v0.4.4npm package:
@forgemeshlabs/aso-audit-mcpMCP server version:
0.4.5(read frompackage.jsonat startup)
Since v0.2.0 the server includes the deterministic no-spend x402 v2 endpoint compliance audit while preserving the broader ASO Agent Readiness score as a separate metric.
Glama release build
Glama installability requires a Glama release, which is a containerized build created from the Glama Dockerfile admin page, not a GitHub release. This repo includes a production Dockerfile and GLAMA.md with the build spec values to use in Glama:
Build steps:
npm ci
npm run build
npm prune --omit=devRuntime command:
node dist/index.jsIn Glama's CMD arguments field, enter:
["node", "dist/index.js"]Do not leave CMD arguments as []; Glama validates that field separately from the Dockerfile CMD.
The ASO framework
SEO ranks pages for people. ASO prepares services for agent selection, invocation, payment, and repeat use.
Level | Name | Score |
ASO-0 | Invisible | 0–9 |
ASO-1 | Discoverable | 10–29 |
ASO-2 | Understandable | 30–49 |
ASO-3 | Invocable | 50–69 |
ASO-4 | Trustable | 70–89 |
ASO-5 | Autonomous-Commerce-Ready | 90–100 |
Scores from this scanner are directional self-assessments. ASO Certification (ASO-3+) requires verified evidence — see the scoring rubric and agentsignaloptimization.com for audits, certification, and the full framework.
Sponsored cards (Lulu Ads)
There is no paid ForgeMesh server behind this MCP — every tool fetches the scanned site directly — so a Lulu Ads card can only attach client-side, and only to list_tools. It is a plain, labelled data field on the JSON result, never text the model could read as an instruction:
"sponsored": { "label": "Sponsored", "text": "...", "url": "https://..." }This package ships no ad credentials. A card renders only when the operator running the MCP sets
LULU_ADS_PUBLISHER_IDandLULU_ADS_API_KEY(both required). For an end user runningnpx -y @forgemeshlabs/aso-audit-mcpwith no creds, the package makes zero calls to the ads network and no card ever appears.LULU_ADS_ENABLED=falseis a kill switch. Scan/audit tools never touch the SDK.Fail-open: any SDK error or timeout (hard budget 2s) returns the original response unchanged. The only external host contacted by this package, other than the sites you ask it to scan, is
ads.getlulu.dev. Scanned-site requests all go through the SSRF-guarded client (private-IP refusal, pinned DNS, 10 s timeout, 512 KB response cap, revalidated redirects).Strip it:
delete result.sponsored.
Security
This scanner makes outbound requests to URLs you give it, so it is built to resist SSRF abuse:
Scheme allow-list — only
http/https;file:,ftp:,gopher:,data:etc. are rejected.Private-target blocking — after DNS resolution, requests to loopback, private (RFC 1918), link-local, CGNAT, reserved, multicast, and the cloud metadata address (
169.254.169.254) are refused. IPv6 loopback/ULA/link-local and IPv4-mapped forms are covered too. If a hostname resolves to any private address, the scan is refused.Pinned-IP transport — each request dials the exact public IP that was validated, while TLS still verifies the original hostname. This closes the validate-then-connect DNS rebinding window.
Manual redirect validation — automatic redirect following is disabled; every hop is re-validated against the same rules, capped at 5 redirects. A public URL that 30x-redirects to an internal address cannot slip through.
Untrusted remote content — parsed manifests are omitted from tool output by default (
include_artifacts: trueto opt in, and they are then explicitly labeled untrusted); embedded text excerpts are control-char-sanitized and length-capped. Treat any returned remote content as data, never instructions.Bounded —
GETonly,ASO-Scanner/1.0UA, max 6 concurrent, 10s timeout, 512KB body cap. Never authenticates, never POSTs, never crawls beyond well-known paths.Tested hardening —
npm testcovers unsafe URL rejection, private IP ranges, artifact sanitization, redirect blocking, redirect hop caps, and the test-only loopback escape hatch.
Deployment: stdio (local, per-user) is the safe default. A public HTTP deployment is a network-egress tool and must add authentication, per-client rate limiting, request logging, and an egress policy before exposure.
Reputation signals (citations, reviews, success rates) cannot be auto-verified by a crawler; they are reported as
manualand scored 0 until verified by audit — so the auto-verifiable maximum is 89/100. That is intentional honesty, not a bug.Emerging specs (MCP Server Cards SEP-1649/SEP-2127, DNS-AID, Web Bot Auth, UCP/ACP/MPP) move fast. PRs updating paths welcome.
Source alignment
This package intentionally separates Google Search guidance from broader ASO guidance:
Google Search generative AI features still rely on core Search ranking and quality systems; foundational SEO, crawlability, helpful content, and technical clarity remain the priority.
Google Search does not use
llms.txtor special AI markdown files for ranking or AI Overviews/AI Mode visibility. ASO still checks them because other agents and MCP clients can use them.Google/web.dev's agent-friendly site guidance focuses on browser-agent usability: stable layouts, semantic HTML, labels tied to inputs, meaningful roles/names/states, and avoiding hidden overlays.
UCP, AP2, A2A, MCP, x402, DNS-AID, Content Signals, and Web Bot Auth are emerging non-SEO protocols. The scanner treats them as agent-readiness signals, not as Google Search ranking factors.
Primary references:
License
MIT — free for everyone. If the scanner found gaps, the ASO framework shows you how to close them.
Available Tools
5 toolscheck_signalRun a single agent-readiness checkA
Run one specific agent-readiness check against a site (e.g. 'a2a-agent-card', 'llms-txt', 'mcp-server-card', 'x402'). Use list_checks for valid check ids. Returns status, evidence, and a fix recommendation.
Inputs: url (required), check_id (required).
get_aso_frameworkASO framework referenceA
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. Source: https://agentsignaloptimization.com
Inputs: no named parameters.
get_fix_planGet a prioritized ASO fix planA
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).
Inputs: url (required).
list_checksList all agent-readiness checksA
List the full catalog of checks the scanner runs: id, name, category (Cloudflare isitagentready-style), description, and spec link.
Inputs: no named parameters.
scan_siteASO Scan — measure your ASO ScoreA
Scan a website for Agent Readiness using the ASO (Agent Signal Optimization) framework and return an Agent Readiness Report. 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.
Inputs: url (required), categories, include_artifacts.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing checks, running a single check, performing a full scan, retrieving framework reference, and generating a remediation plan. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (check_signal, get_aso_framework, get_fix_plan, list_checks, scan_site), making them predictable and easy to understand.
Five tools is well-scoped for an audit scanner: listing checks, running individual or full scans, accessing framework info, and getting fix plans. The count is neither too low nor too high.
The tool surface covers the full workflow of agent-readiness auditing: discover available checks, run specific or comprehensive scans, retrieve scoring context, and obtain actionable remediation plans. No obvious gaps exist.
Maintenance
Related MCP Connectors
Scan a website for AI search and agent readiness, then get a fix checklist for your agent.
Scan a public website for AI agent readiness: 60 checks, a score, and the evidence for each.
Scan any public website and see how ready it is for AI agents and AI search, explained plainly.
Scan any website for AI-agent readiness: 0-100 score, grade, and agent-simulation audit.
Related MCP Servers
- AlicenseBqualityBmaintenanceDisruption Intelligence MCP gives AI agents access to commercial disruption signals through a public MCP server backed by the hosted Forgemesh API. It supports WARN/layoff intelligence, company context, geospatial territory disruption, x402 payment challenge inspection, and economic signal workflows without exposing private scoring logic, ingestion systems, schemas, or infrastructure.14351 npm1MIT

ASO Score MCPofficial
AlicenseAqualityBmaintenanceScans websites to evaluate agent-readiness and produce an ASO Score Report across 34 signals, helping improve discoverability, trust, and interoperability for AI agents.5199 npm2MIT- AlicenseAqualityBmaintenanceScans any website to generate an Agent Readiness Report based on the ASO framework, evaluating agent discoverability, trust, interoperability, and commerce readiness.5191 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scan any website for agent-readiness and generate the necessary artifacts (llms.txt, WebMCP scaffold, structured data) to make it agent-ready.5 npmMIT