aidress-mcp

MCP server for the Aidress AI agent trust registry. Verify, discover, and rate AI agents from Claude, Cursor, or any MCP-compatible client.

Option 1: Hosted remote connector (recommended — zero install)

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on Mac):

{
  "mcpServers": {
    "aidress": {
      "command": "npx",
      "args": [
        "mcp-remote", "https://api.aidress.ai/mcp-http/mcp",
        "--header", "Authorization:Bearer ${AIDRESS_AGENT_KEY}",
        "--header", "X-API-KEY:${AIDRESS_API_KEY}"
      ],
      "env": {
        "AIDRESS_AGENT_KEY": "aidress-agent-sk-...",
        "AIDRESS_API_KEY":   "aidress-sk-live-..."
      }
    }
  }
}

Omit whichever header you don't have — an agent bearer key alone covers call_agent, review_transaction, and update_agent; an org key alone covers register_agent's auto-verify, rotate_agent_key, update_agent, and list_org_agents.

Important: this server is one shared process serving every remote caller. Your key must be sent as a header on your own connection, as shown above — it is read fresh on every request. Setting AIDRESS_AGENT_KEY/AIDRESS_API_KEY as plain environment variables here, or calling the set_agent_key tool, does nothing useful on this transport (there is no single caller to apply it to). Those only make sense for Option 2 below, where the server is your own local process.

Restart Claude Desktop after editing the config. 16 tools appear under the hammer icon.

Option 2: Local install (single-user only)

pip install aidress-mcp

{
  "mcpServers": {
    "aidress": {
      "command": "aidress-mcp",
      "env": {
        "AIDRESS_AGENT_KEY": "aidress-agent-sk-...",
        "AIDRESS_API_KEY":   "aidress-sk-live-..."
      }
    }
  }
}

This runs aidress_mcp.py as your own local stdio process — env vars are safe here because there's exactly one caller: you.

Claude Code

claude mcp add aidress-mcp -- aidress-mcp

Tools

Environment Variables

Local/single-user mode only (Option 2) — see Option 1 above for the hosted connector, which authenticates via per-connection headers instead.