Can other agents read your agent card?
An agent introduces itself with a card published at /.well-known/agent-card.json. It is the only document another agent reads before deciding to call you. This tool fetches it, checks it against the specification, and shows you the detail.
Conformant card
Nothing the specification requires is missing.
What the card declares
- Name
- The Website Specification
- Provider
- Joost de Valk
- Agent version
- 0.1.0
- Protocol version
- 1.0
- Transport
- JSONRPC
- Endpoint
- https://mcp.specification.website/a2a/v1
- Card shape
- v1.0
- Location
- standard location
- Skills
- 3
- Response time
- 106 ms
Findings
- NoteCard not signed: nothing attests that it comes from its author
signatures
Declared skills
- Search the specFree-text search across every spec page. Returns ranked results with title, status, category, canonical URL, and a body excerpt.
- Fetch a spec topicFetch the full canonical Markdown of one spec page by slug. Send a text part of the form `topic:<slug>` — for example `topic:content-security-policy` or `topic:llms-txt`.
- Audit a website against the specPair this agent with a browsing agent: ask it for the relevant required and recommended topics for a category (security, seo, accessibility, performance, privacy, i18n, resilience, agent-readiness, well-known, foundations) and the audit plan falls out.
Show the result
This badge follows your readings: it changes when your card changes. Paste it in your README.
Markdown
[](https://kopass.app/a2a/validator?url=https://specification.website)HTML
<a href="https://kopass.app/a2a/validator?url=https://specification.website"><img src="https://kopass.app/a2a/badge/aHR0cHM6Ly9zcGVjaWZpY2F0aW9uLndlYnNpdGU.svg" alt="A2A card" height="20"></a>The rules come from the protocol's specification/a2a.proto file, where every required field is marked as such. Nothing is added.
Cards read here feed the KoPass daily reading: 229 agents followed, 215 of which answered on the last pass.