Developer Tools

kopass.app

Serves daily-updated counts of A2A and MCP ecosystem projects and provides search and lookup tools for developer tools, MCP servers, and A2A agents.

1 endpoint7 known toolsFirst detected October 2, 2026Last detected October 2, 2026

ENDPOINT 1

https://kopass.app/mcp

No auth detected

MCP server metadata

Name: kopass
Version: 1.0.0

Capabilities

tools

Server instructions

KoPass answers with measurements, never with opinions, and every figure carries the date it was taken. Use a2a_ecosystem or mcp_ecosystem for ecosystem sizes, search_tools for the developer catalogue, find_agents_by_capability for deployed A2A agents that still answer, and validate_agent_card to check one card against the specification.

Known tools 7

a2a_ecosystem

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.

Inferred read-only

mcp_ecosystem

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.

Inferred read-only

search_tools

Search the KoPass catalogue of developer tools, libraries, CLIs, MCP servers and agent skills.

Inferred read-only

find_agents_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 reading.

Inferred read-only

agent_record

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.

Inferred read-only

a2a_conformance

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.

Inferred read-only

validate_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 v1.0.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.kopass]
url = "https://kopass.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "kopass": {
      "type": "http",
      "url": "https://kopass.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: kopass
Remote MCP URL: https://kopass.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "kopass": {
      "url": "https://kopass.app/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "kopass": {
      "type": "http",
      "url": "https://kopass.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "kopass",
  "transport": "streamable-http",
  "url": "https://kopass.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for kopass.app was fetched 2026-10-03T06:59:40.127Z.

Trust status Neutral

kopass.app is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.