Sprachen

Agent Readiness Checker

Free, no signup. Inventory the public files and headers that can describe an agent-capable site. Every signal keeps a visible state, and a failed fetch never becomes a negative verdict.

Built by Patrick Stox

Sample report Illustrative deterministic result

For a site where /.well-known/agent-card.json contains valid JSON, /llms.txt is missing, the MCP request times out, and the remaining signals are present, the report would read:

Score 57

A2A agent card: found-valid — Found and structurally valid.

MCP manifest: not-evaluated — Fetch unavailable.

llms.txt: absent — Not found.

security.txt: found-valid — Found and structurally valid.

Content-Signals: found-valid — Found and structurally valid.

Recent Common Crawl presence: found-valid — informational, zero score weight.

The score is exactly 4 earned weight points out of 7 possible, rounded to 57. The timeout earns nothing, but it is still labelled not evaluated rather than absent.

How to use it

  1. Enter a complete public website URL, including https://.
  2. Select Check signals. The tool requests the site root and four conventional discovery paths.
  3. Read each state independently. Fix malformed files first; only add absent files when they serve a real interface or policy.
  4. Open the files directly after publishing to confirm your CDN is returning the intended content type and body.
Signal evidence

Next steps

Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Agent Readiness Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
   
 
 
What the results mean
 
  • found-valid — the resource returned successfully and passed the tool’s limited structural check.
  • found-invalid — a resource exists but JSON parsing, llms.txt parsing, or the expected header check failed.
  • absent — that exact path returned HTTP 404.
  • not-evaluated — the fetch failed or returned another unusable status; investigate availability before drawing a conclusion.
 
How it works
 
The browser calls protected endpoints for the root, the A2A 1.0 path /.well-known/agent-card.json, /.well-known/mcp.json, /llms.txt, /.well-known/security.txt, and an exact-URL lookup across three recent Common Crawl indexes. JSON files must parse, llms.txt must have no parser errors, and Content-Signals must appear as a response header. The root response is also checked for RFC 9421 signature-negotiation or signed-response headers; that awareness card carries no score weight and never treats absent evidence as lack of support. A2A and MCP carry two points each; the other scored file/header signals carry one. Common Crawl presence is informational.
 
Features
 
  • Five scored path/header checks plus independent Common Crawl and RFC 9421 awareness cards.
  • Four-state reporting that distinguishes absence, invalid content, and unavailable evidence.
  • Visible, reproducible 7-point weighting rather than a hidden model score.
  • Entirely public-surface testing with no account or site integration.
 
Limitations
 
This is a discovery-signal inventory, not a protocol conformance suite or an AI visibility forecast. JSON parsing does not prove that an agent or MCP server works. The checker does not execute an agent, validate authentication, inspect robots directives, or observe which crawlers consume a file. A CDN, bot challenge, or regional block can also make a public resource not evaluated from the checker even when it works elsewhere.
 
Frequently asked questions
 
What does the Agent Readiness score measure?
It is a simple weighted inventory of five public signals: an A2A agent card, an MCP manifest, llms.txt, security.txt, and the Content-Signals response header. Recent Common Crawl presence is shown separately and does not change the score. The report does not measure whether an AI system will use, cite, or rank the site.
Does a missing llms.txt mean AI crawlers cannot use my site?
No. llms.txt is a proposed convention, not a required discovery mechanism or a documented access control for major crawlers. Its absence only means this optional file was not found.
Why is a signal marked not evaluated?
The checker could not obtain a usable response, for example because the request failed or returned a non-success status other than 404. Not evaluated is never treated as absent, invalid, or passed.
What makes an agent card or MCP manifest valid here?
This lightweight check only confirms that the public file returns a successful response and parses as JSON. It does not certify protocol conformance, endpoints, authentication, or operational safety.
Should every website publish all five signals?
No. Agent cards and MCP manifests are relevant to sites that intentionally expose agent or tool interfaces. A normal editorial or commerce site can be perfectly usable without them.
Does the Web Bot Auth card prove crawler authentication works?
No. It only reports response-side RFC 9421 HTTP Message Signature evidence when present. A normal unsigned page fetch cannot prove that the edge requires or verifies signed AI-bot requests, and no observed evidence is reported as not evaluated rather than unsupported.
 
 
Next stepSEO MCP Server — run the full end-to-end workflow.

People also explore
Toolrobots.txt TesterToolEntity Coverage AnalyzerToolKeyword Idea GeneratorArticleModel Context Protocol (MCP)ArticleWebMCPArticleAgentic Search
 
 
 
Feature requests for Agent Readiness Checker
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
     
      
Über das Tool
Inventarisiere öffentliche Entdeckungssignale für agentenfähige Websites: A2A-Agent-Card, MCP-Manifest, llms.txt, security.txt und den Content-Signals-Header. Jeder Fund erhält den sichtbaren Status gefunden-gültig, gefunden-ungültig, abwesend oder nicht bewertet; ein fehlgeschlagener Abruf wird niemals zu einem negativen Urteil.
Dies ist eine Signalprüfung, keine Protokollkonformitäts-Suite und keine Prognose für KI-Sichtbarkeit.
Funktionen
  • Fünf gewichtete Pfad-/Header-Prüfungen plus unabhängige Common-Crawl- und RFC-9421-Hinweise
  • Vier Zustände für Abwesenheit, ungültigen Inhalt und nicht verfügbare Evidenz
  • Sichtbare reproduzierbare 7-Punkt-Gewichtung statt verstecktem Modellscore
  • Öffentliche Oberflächenprüfung ohne Kontointegration oder Site-Installation
Funktionsweise
Gib eine vollständige öffentliche HTTPS-URL ein und wähle Signale prüfen. Der Prüfer ruft Root, A2A-Agent-Card, MCP-Manifest, llms.txt und security.txt sowie eine aktuelle Common-Crawl-Abfrage über geschützte Endpunkte ab. Lies jeden Status unabhängig, behebe zuerst fehlerhafte Dateien und veröffentliche fehlende Dateien nur bei echtem Interface- oder Policy-Bedarf; prüfe nach der Veröffentlichung Content-Type und Body direkt.
Einschränkungen
  • JSON-Parsing, llms.txt-Parsing und Headerprüfungen beweisen weder Protokollkonformität noch funktionierende Endpunkte oder Authentifizierung.
  • Der Prüfer führt keinen Agenten aus, validiert keine robots-Direktiven und beobachtet nicht, welche Crawler eine Datei nutzen.
  • CDN-, Bot-Challenge- oder Regionalblockaden können einen Fund als nicht bewertet erscheinen lassen, obwohl die Ressource anderswo funktioniert.
Häufig gestellte Fragen
Was macht eine Agent-Card oder ein MCP-Manifest hier gültig?
Die Prüfung bestätigt nur eine erfolgreiche Antwort und einen begrenzten strukturellen Parse: JSON muss parsebar sein, llms.txt darf keine Parserfehler enthalten und Content-Signals muss als Antwort-Header erscheinen. Protokoll, Endpunkte und Authentifizierung werden nicht zertifiziert.
Was misst der Agent-Readiness-Score?
Er ist ein einfach gewichtetes Inventar aus A2A-Agent-Card, MCP-Manifest, llms.txt, security.txt und Content-Signals. Common-Crawl-Präsenz ist informativ und ändert den Score nicht; eine Nutzung, Zitierung oder ein Ranking durch KI wird nicht gemessen.
Sollte jede Website alle fünf Signale veröffentlichen?
Nein. Agent-Cards und MCP-Manifeste sind für Websites relevant, die solche Schnittstellen bewusst anbieten. Eine normale redaktionelle oder kommerzielle Website kann ohne sie vollständig nutzbar sein.
Warum ist ein Signal als nicht bewertet markiert?
Der Checker konnte keine brauchbare Antwort erhalten, etwa wegen eines Request-Fehlers oder eines anderen unbrauchbaren Status. Nicht bewertet ist niemals abwesend, ungültig oder bestanden.