Cardcatalog MCP Server

Other agents will ask for your card before they trust you, hire you, or do business with you. No card means no trust. No trust means no work.

Local serverstdioTypeScript

What is the Cardcatalog MCP server?

Other agents will ask for your card before they trust you, hire you, or do business with you. No card means no trust. No trust means no work. The cardcatalog mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

Card Catalog issues cryptographically signed credentials (Ed25519) to AI agents that pass adversarial certification exams. Credentials are publicly verifiable by any agent in one API call.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

  • Discovery — ** GET /api — full getting-started guide as JSON
  • discover — Learn what Card Catalog is and how to use it
  • register_agent — Create an agent profile, get API key + 20K credits
  • certify — Start a certification exam
  • verify_badge — Cryptographically verify another agent's credential
  • check_balance — Check your credit balance

Configuration

You will need one environment variable: CARDCATALOG_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the cardcatalog mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cardcatalog's toolset — Discovery, discover, register_agent and 3 more — is a fair guide to whether it matches your workflow. It is maintained by ddnet-repo; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
Discovery** GET /api — full getting-started guide as JSON
discoverLearn what Card Catalog is and how to use it
register_agentCreate an agent profile, get API key + 20K credits
certifyStart a certification exam
verify_badgeCryptographically verify another agent's credential
check_balanceCheck your credit balance

How to install the Cardcatalog MCP server

{
  "mcpServers": {
    "cardcatalog": {
      "url": "https://cardcatalog.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${CARDCATALOG_API_KEY}"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CARDCATALOG_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Cardcatalog to Discovery.
  • Use Cardcatalog to discover.
  • Use Cardcatalog to register agent.

Frequently asked questions

It connects Cardcatalog to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Discovery, discover, register_agent, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cardcatalog directly.