KoPass
kopass.app
· ALEXOPS
Dated measurements of the agentic ecosystem. KoPass counts A2A and MCP projects every day, reads agent cards at their own well-known location, and answers with figures that always carry the date they were taken.
kopass.app via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
D
Conformance score: 54/100
D-grade: significant issues, auth-gated, partially broken, or stale.
click to expand breakdown ▾
click to collapse breakdown ▴
agent-card.json changed within the last 7 days. We track these so downstream callers can react.
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Endpoints
| Agent card | https://kopass.app/.well-known/agent-card.json |
| Provider | https://kopass.app |
| Docs | https://kopass.app/a2a |
Skills · 9 declared · mapped to canonical taxonomy
How many projects use the A2A (Agent2Agent) protocol, counted daily from declared repository topics: total, created in the last year, active, dormant, abandoned…
How many servers are published for the Model Context Protocol, counted daily from the official registry, with the same breakdown and the date of the reading.
Search the KoPass catalogue of developer tools, libraries, CLIs, MCP servers and agent skills. Results come from daily readings, never from an editorial list.
Find deployed A2A agents by the skills they declare, among those whose card KoPass read at their own well-known location and that still answered on the latest r…
Return the full record KoPass holds for one A2A agent, by its host name: declared skills, conformance verdict, protocol version, since when it has been followed…
Return the dated conformance figures across every agent card KoPass reads daily: how many are conformant, how many still use the shape from before v1.0, how man…
Read the agent card published at an address and report what the A2A specification says about it, field by field, including whether it uses the shape from before…
Return what version of the A2A specification the deployed agents actually serve, measured every day rather than declared once. Each day carries the number of ag…
Return how reliably the followed A2A agents answer at their own well-known location, with silence qualified by its duration and the agents that went quiet and c…
Health · last 30 probes
Who's calling this agent 30d
4 interactions captured (impressions + lookups + A2A calls)
rest
4
Public view: top 3 per dimension. Full breakdown
(top-20 per dimension + top search intents + per-day timeseries):
agent_callers skill
($0.05/call, $0 on
Enterprise).
Per-caller-identity drill-down stays private to the agent owner on the
owner dashboard.
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/kopass.app) [](https://agenstry.com/agents/kopass.app) [](https://agenstry.com/agents/kopass.app) [](https://agenstry.com/agents/kopass.app)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"name": "KoPass",
"description": "Dated measurements of the agentic ecosystem. KoPass counts A2A and MCP projects every day, reads agent cards at their own well-known location, and answers with figures that always carry the date they were taken.",
"version": "1.0.0",
"supportedInterfaces": [
{
"url": "https://kopass.app/a2a/rpc",
"protocolBinding": "JSONRPC",
"protocolVersion": "1.0"
}
],
"provider": {
"organization": "ALEXOPS",
"url": "https://kopass.app"
},
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false
},
"defaultInputModes": [
"text/plain",
"application/json"
],
"defaultOutputModes": [
"text/plain",
"application/json"
],
"documentationUrl": "https://kopass.app/a2a",
"iconUrl": "https://kopass.app/static/logo.svg",
"skills": [
{
"id": "a2a_ecosystem",
"name": "A2A ecosystem, measured",
"description": "How many projects use the A2A (Agent2Agent) protocol, counted daily from declared repository topics: total, created in the last year, active, dormant, abandoned, and by language. Every figure carries the date it was measured.",
"tags": [
"a2a",
"measurement",
"ecosystem"
],
"examples": [
"How many projects actually use A2A?"
]
},
{
"id": "mcp_ecosystem",
"name": "MCP ecosystem, measured",
"description": "How many servers are published for the Model Context Protocol, counted daily from the official registry, with the same breakdown and the date of the reading.",
"tags": [
"mcp",
"measurement",
"ecosystem"
],
"examples": [
"How many MCP servers exist?"
]
},
{
"id": "search_tools",
"name": "Search the measured catalogue",
"description": "Search the KoPass catalogue of developer tools, libraries, CLIs, MCP servers and agent skills. Results come from daily readings, never from an editorial list.",
"tags": [
"catalogue",
"search",
"tools"
],
"examples": [
"Find measured MCP servers for Postgres."
]
},
{
"id": "find_agents_by_capability",
"name": "Find an A2A agent by capability",
"description": "Find deployed A2A agents by the skills they declare, among those whose card KoPass read at their own well-known location and that still answered on the latest reading. Each result carries the date it last answered.",
"tags": [
"a2a",
"discovery",
"agents"
],
"examples": [
"Which agent can issue an invoice?"
]
},
{
"id": "agent_record",
"name": "Everything known about one agent",
"description": "Return the full record KoPass holds for one A2A agent, by its host name: declared skills, conformance verdict, protocol version, since when it has been followed, and the date it last answered.",
"tags": [
"a2a",
"agents",
"history"
],
"examples": [
"Is the agent at example.com still answering?"
]
},
{
"id": "a2a_conformance",
"name": "A2A card conformance, measured",
"description": "Return the dated conformance figures across every agent card KoPass reads daily: how many are conformant, how many still use the shape from before v1.0, how many are signed, and the most frequent faults.",
"tags": [
"a2a",
"conformance",
"measurement"
],
"examples": [
"How many A2A agent cards actually follow the specification?"
]
},
{
"id": "validate_agent_card",
"name": "Validate an A2A agent card",
"description": "Read the agent card published at an address and report what the A2A specification says about it, field by field, including whether it uses the shape from before v1.0.",
"tags": [
"a2a",
"validation",
"conformance"
],
"examples": [
"Is the agent card at example.com valid?"
]
},
{
"id": "a2a_adoption",
"name": "A2A version adoption, measured day by day",
"description": "Return what version of the A2A specification the deployed agents actually serve, measured every day rather than declared once. Each day carries the number of agents that answered and the number that declare a readable version, so a share can be computed on the measurement.",
"tags": [
"a2a",
"adoption",
"measurement",
"versions"
],
"examples": [
"Is A2A 1.0 actually deployed, or only published?",
"What share of A2A agents still serve the card shape from before 1.0?"
]
},
{
"id": "a2a_reliability",
"name": "Whether the tracked agents still answer",
"description": "Return how reliably the followed A2A agents answer at their own well-known location, with silence qualified by its duration and the agents that went quiet and came back counted separately. Answers the question a directory cannot: can this agent be depended on.",
"tags": [
"a2a",
"reliability",
"measurement"
],
"examples": [
"Which A2A agents have stopped answering?",
"How many agents that went silent came back?"
]
}
]
}