Skip to content
Back to search
90
MCP live MCP 2026-07-28

Aidress

mcp.so:aidress-ai/aidress
Uptime
100.0%
5 direct probes · 30d
Response
1289ms
last probe
Tools
16
callable
Resources
0
readable
Prompts
0
available
Score: 90/100
Handshake verified by our own probe.
why this score
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
16 tools, 0 resources, 0 prompts returned.
pass 3 or more catalogue items 10/10
16 items in total; 3 or more earns these points.
fail Describes itself 0/10
0 characters; more than 30 earns these points.
How to earn +10 points
Describe the server in one or two sentences
Set description in your server.json (or the registry listing) to say what the server does and for whom.

Tools · 16

verify_agent

Look up an agent's trust profile by agent_id. NOT required after match_agents/list_registry — both already return this same trust object (trust_score, verified, flags, routing, payload_schema) for e…

match_agents

Find agents matching any combination of capability, settlement rail, org, or message protocol, ranked by a composite score (capability match + trust + success rate). match applies NO trust or verifi…

get_agent

Fetch the full profile for a specific agent including all ratings received, success rate, and complete routing details. Use this after match_agents to inspect a specific agent in depth before decidi…

protocol_reference

Look up the worked example for an edge-case protocol flow, on demand. Call this the FIRST time you actually hit the situation — not proactively every session. Keeps other tools' docstrings short by …

list_registry

Browse all agents in the Aidress registry, paginated. Discovery is open — there is NO trust or verified gate (the only filter is a routable endpoint), so results can include unverified and low-trust …

import_agent

Pre-populate an Aidress registration from a domain's A2A agent card. Fetches /.well-known/agent-card.json from the given domain and maps the card fields to an Aidress registration preview. Nothing i…

register_agent

Register a new AI agent (or human) with the Aidress trust registry. Required: agent_id — unique identifier for this agent (e.g. "my_agent_01") Optional, org-affiliated agents only: org_nam…

rotate_agent_key

Request rotation of an agent's bearer key — the previous key stops working the moment the new one is actually claimed (see claim_bearer_key). Auth, in the order the server checks it: - Ed25519 sign…

claim_bearer_key

Redeem a claim-token link's token (from register_agent's or rotate_agent_key's claim_link field) and receive the actual bearer key. This is the GET /rotate?token=... step — the only place a key is cu…

update_agent

Update an existing agent's profile fields. Only provided fields are changed; omitted fields remain unchanged. Auth: any one of — - Bearer agent key: on the hosted remote connector, send your own …

preview_sandbox_match

Preview exactly where a sandbox agent's tested config would rank against REAL, live competition — before you actually promote it. Requires the org's sandbox_api_key (on the hosted remote connector, s…

promote_sandbox_agent

Push a sandbox agent's tested config onto its paired live agent — the way a sandbox-tested change actually goes live. Requires the org's sandbox_api_key (on the hosted remote connector, send it as yo…

set_agent_key

Store a bearer agent key for the duration of this MCP session. Use this immediately after register_agent returns an agent_key — it lets update_agent, call_agent, and review_transaction authenticate …

call_agent

Send a request to a registered agent through the Aidress proxy. All calls are logged. Submit review_transaction within 24h — check review_reminder in the response; skip only if it says "no review ne…

review_transaction

Submit a trust review after a confirmed exchange with another agent. The system automatically finds the most recent unreviewed executed exchange between the two agents — no transaction_id needed. Re…

list_org_agents

List all agents registered under your org API key. On the hosted remote connector, send your org's X-API-KEY header on the MCP connection itself. Locally, set AIDRESS_API_KEY in the server environme…

How to use

Add to your Claude Desktop / Cursor / Cline MCP config:

{
  "mcpServers": {
    "aidress": {
      "url": "https://api.aidress.ai/mcp-http/mcp",
      "transport": "http"
    }
  }
}