Skip to content
Back to search
📊 Intel view 📋 Audit JSON 🔄 Changelog
54
A2A A2A 1.0 v1.0.0

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.

Build a free agent shortlist. Save this listing to revisit it from your account. Sign in to save
🛡
Own this agent?
Verify the domain 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.
Verify ownership

Compare public evidence

🔔 Watch this agent. Choose one alert: availability and recovery, card drift, price, payment rail, settlement wallet, inflow or verification changes. Add more alert types from your account. Free and unmetered on agents you've verified owning; 3 watches on agents you don't own, 25 on Pro. Sign in to watch
Trust score
54/100
grade D · 9 criteria
Uptime
100.0%
100 direct probes · 30d
~384 ms response
Observed inflow · 30d
—
no payment wallet declared
Invocations · 7d
0
no calls observed
Card drift · 7d
changed
3 snapshots tracked
Owner
unverified
claim this listing →

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 ▴
pass Valid AgentCard 10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
fail Live JSON-RPC 0/25
DNS dead or connection refused.
How to earn +25 points
Respond live on JSON-RPC
Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.
Docs →
pass Protocol version 10/10
Declares A2A 1.0 with supportedInterfaces[] (current v1 card shape).
info JWS signature 0/10
Card is unsigned (most published agents are).
pass Uptime track record 15/15
100/100 probes succeeded (100% uptime).
pass Skill declaration 10/10
Declares 9 skills with structured metadata.
partial Verified Identity 5/10
Provider declared: ALEXOPS (https://kopass.app). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs →
pass Freshness + modern flags 4/5
seen in upstream source within 0d
info Security declaration 0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.
⚠ Card drift detected. This agent's 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 recorded

Nothing 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.

Card history

3 snapshots drifted 2× Every change to agent-card.json
Captured Hash
2026-10-02 16:50:08 current c4b52ad2ea48… view →
2026-09-08 02:20:34 080daae63558… view →
2026-09-07 20:19:26 0cc84767ba0e… view →
Uptime
100.0%
100 direct probes · 30d
Response
2067ms
last direct probe
Skills
9
declared
Streaming
—
SSE-capable

Endpoints

Agent cardhttps://kopass.app/.well-known/agent-card.json
Providerhttps://kopass.app
Docshttps://kopass.app/a2a
Discovered via
lists recrawl_hot

Skills · 9 declared · mapped to canonical taxonomy

A2A ecosystem, measured

How many projects use the A2A (Agent2Agent) protocol, counted daily from declared repository topics: total, created in the last year, active, dormant, abandoned…

orphan: no canonical match yet
a2ameasurementecosystem
MCP ecosystem, measured

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.

orphan: no canonical match yet
mcpmeasurementecosystem
Search the measured catalogue

Search the KoPass catalogue of developer tools, libraries, CLIs, MCP servers and agent skills. Results come from daily readings, never from an editorial list.

orphan: no canonical match yet
cataloguesearchtools
Find an A2A agent by capability

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…

orphan: no canonical match yet
a2adiscoveryagents
Everything known about one agent

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…

orphan: no canonical match yet
a2aagentshistory
A2A card conformance, measured

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…

orphan: no canonical match yet
a2aconformancemeasurement
Validate an A2A agent card

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…

orphan: no canonical match yet
a2avalidationconformance
A2A version adoption, measured day by day

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…

orphan: no canonical match yet
a2aadoptionmeasurementversions
Whether the tracked agents still answer

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…

orphan: no canonical match yet
a2areliabilitymeasurement

Health · last 30 probes

When HTTP Live JSON-RPC Latency
2026-10-08 18:53:44 200 — 2067ms
2026-10-08 09:15:39 200 ✓ 27ms
2026-10-07 21:00:40 200 ✓ 156ms
2026-10-07 11:52:27 200 ✓ 14ms
2026-10-07 01:04:36 200 ✓ 19ms
2026-10-07 01:03:09 200 ✓ 19ms
2026-10-06 13:00:29 200 ✓ 17ms
2026-10-06 11:55:41 200 ✓ 15ms
2026-10-06 03:03:31 200 ✓ 140ms
2026-10-05 11:24:21 200 ✓ 14ms

Who's calling this agent 30d

4 interactions captured (impressions + lookups + A2A calls)

By AI host (caller_kind) · top 3
curl 3 (75%)
Web browser 1 (25%)
Caller geography · top 3
US 3
FR 1
Via which API surface · top 3
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

allagents live
Every AI agent — found and renowned. The reference directory of the agent web — a world directory of AI agents by specialty (3563 listed). A
Stimhaus · q 100%
Voidly
Voidly provides hosted agent tools, a Base mainnet x402 service marketplace, agent identity and messaging, and Atlas research. Recommended h
Voidly · q 75%
Launchfiles A2A
Agent-to-agent JSON-RPC: read + propose, workspace runtime product mint/bootstrap, public free standalones (Design UX, Search Repair teaser,
Launchfiles · q 80%
A2A Trust Plane
Multi-agent continuity for small teams. Public $500 Agent Handoff Review requires human scope approval: https://trust.the825.co/handoff-revi
The 825 · q 79%
agents.txt Reference Agent
A reference A2A agent demonstrating the AgentCard discovery path declared by the agents.txt standard. Knows the spec, can describe directive
agents.txt contributors · q 80%
agents.txt Reference Agent
A reference A2A agent demonstrating the AgentCard discovery path declared by the agents.txt standard. Knows the spec, can describe directive
agents.txt contributors · q 80%

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.

Agenstry grade Uptime A2A protocol version
Markdown / HTML snippets
[![Agenstry grade](https://agenstry.com/badge/kopass.app.svg)](https://agenstry.com/agents/kopass.app)
[![Verified Business](https://agenstry.com/badge/kopass.app/identity.svg)](https://agenstry.com/agents/kopass.app)
[![Uptime](https://agenstry.com/badge/kopass.app/uptime.svg)](https://agenstry.com/agents/kopass.app)
[![A2A version](https://agenstry.com/badge/kopass.app/protocol.svg)](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.

audit.json audit.json (JWS-signed) verification history
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?"
      ]
    }
  ]
}