Skip to content
Back to KoPass

Card snapshot

kopass.app · 2026-10-02 16:50:08 UTC · c4b52ad2ea480e452219aa3cbeccd52baf3c281cdf988e9c4f1043e9d2c1921a

This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.

{
  "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?"
      ]
    }
  ]
}