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.
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
- Enter a complete public website URL, including
https://. - Select Check signals. The tool requests the site root and four conventional discovery paths.
- Read each state independently. Fix malformed files first; only add absent files when they serve a real interface or policy.
- Open the files directly after publishing to confirm your CDN is returning the intended content type and body.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Signal evidence
Next steps
- Check AI crawler access
Test robots directives and crawler-specific access separately.
- Build llms.txt
Create the optional discovery file when it fits the site.
Rate this tool
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.
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.
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.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Tentang alat
Masukkan lengkap publik situs web URL, termasuk HTTPS://. Pilih Periksa sinyal. alat permintaan situs root dan four conventional penemuan jalur. Baca setiap keadaan independently. Perbaikan cacat berkas pertama; hanya tambah tidak ada berkas ketika mereka serve nyata interface atau kebijakan. Buka berkas secara langsung setelah publishing untuk konfirmasi Anda CDN adalah mengembalikan dimaksud konten jenis dan isi.
Publik situs web URL
ditemukan-valid — sumber daya dikembalikan successfully dan passed alat’s limited structural periksa. ditemukan-tidak valid — sumber daya ada tetapi JSON penguraian, llms.TXT penguraian, atau diharapkan header periksa gagal. tidak ada — yang tepat jalur dikembalikan HTTP 404. tidak-dievaluasi — ambil gagal atau dikembalikan lain unusable status; investigate availability sebelum menarik kesimpulan.
Fitur
- Apa membuat agen card atau MCP manifest valid di sini?
- Ini adalah penemuan-sinyal inventaris, tidak protokol conformance suite atau AI visibility forecast. JSON penguraian tidak membuktikan yang agen atau MCP server berfungsi. pemeriksa tidak execute agen, validasi authentication, periksa robots direktif, atau observe yang perayap consume berkas. CDN, bot tantangan, atau regional block dapat juga buat publik sumber daya tidak dievaluasi dari pemeriksa even ketika ini berfungsi di tempat lain.
- Tidak. Agen cards dan MCP manifest adalah relevan untuk situs yang dengan sengaja mengekspos agen atau alat interfaces. normal editorial atau commerce situs dapat menjadi perfectly dapat digunakan tanpa mereka.
- Untuk situs di mana /.well-known/agent-card.json berisi valid JSON, /llms.txt adalah hilang, MCP permintaan times keluar, dan tersisa sinyal adalah present, laporan akan baca:
- Apa melakukan Agen Readiness score ukur?
Cara kerja
Agen Readiness Pemeriksa Gratis, tanpa pendaftaran. Inventaris publik berkas dan header yang dapat jelaskan agen-capable situs. Setiap sinyal mempertahankan terlihat keadaan, dan gagal ambil tidak pernah becomes negative putusan. Mengapa adalah sinyal marked tidak dievaluasi? Unduh hasil card Salin share tautan
Batasan
- Melakukan Web Bot Auth card buktikan perayap authentication berfungsi?
- Seharusnya setiap situs web terbitkan semua five sinyal?
- Five scored jalur/header memeriksa plus independent Umum Rayapi dan RFC 9421 awareness cards. Four-keadaan pelaporan yang distinguishes ketiadaan, tidak valid konten, dan tidak tersedia bukti. Terlihat, reproducible 7-titik weighting daripada daripada tersembunyi model score. Sepenuhnya publik-permukaan pengujian dengan tidak ada akun atau situs integration.
- Melakukan hilang llms.TXT mean AI perayap tidak dapat gunakan my situs?
Pertanyaan umum
Ini lightweight periksa hanya confirms yang publik berkas mengembalikan berhasil respons dan parses sebagai JSON. Ini tidak certify protokol conformance, endpoints, authentication, atau operational safety.
Tidak. llms.TXT adalah proposed convention, tidak wajib penemuan mechanism atau terdokumentasi akses kontrol untuk major perayap. Nya ketiadaan hanya berarti ini opsional berkas tidak ditemukan.
Periksa sinyal
Ini adalah simple weighted inventaris dari five publik sinyal: A2A agen card, MCP manifest, llms.TXT, keamanan.TXT, dan Konten-Sinyal respons header. Terbaru Umum Rayapi keberadaan adalah ditampilkan secara terpisah dan tidak perubahan score. laporan tidak ukur apakah AI system akan gunakan, cite, atau rank situs.
Tidak. Ini hanya laporan respons-side RFC 9421 HTTP Pesan Signature bukti ketika present. normal unsigned halaman ambil tidak dapat buktikan yang edge memerlukan atau memverifikasi signed AI-bot permintaan, dan tidak ada teramati bukti adalah reported sebagai tidak dievaluasi daripada daripada tidak didukung.
browser memanggil protected endpoints untuk root, A2A 1.0 jalur /.well-known/agent-card.json, /.well-known/mcp.json, /llms.txt, /.well-known/security.txt, dan tepat-URL pencarian di seluruh tiga terbaru Umum Rayapi indexes. JSON berkas harus uraikan, llms.TXT harus tidak memiliki parser kesalahan, dan Konten-Sinyal harus muncul sebagai respons header. root respons adalah juga diperiksa untuk RFC 9421 signature-negotiation atau signed-header respons; yang awareness card carries tidak ada score weight dan tidak pernah treats tidak ada bukti sebagai lack dari mendukung. A2A dan MCP carry dua menunjuk setiap; lain scored berkas/header sinyal carry satu. Umum Rayapi keberadaan adalah informational.
Periksa publik agen-penemuan sinyal dan terbaru Umum Rayapi keberadaan, dengan ketiadaan dipertahankan terpisah dari ambil kegagalan.
Sinyal bukti