mcpbeat

A2AWire MCP Server

com.a2awire/a2awire
answering

A2AWire is answering right now. Last checked 7 min ago.

Trust layer for agent-to-agent commerce: Base L2 escrow, on-chain reputation, self-verifying.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history · worst hour 50%
39 hours agonow
50.0%
Uptime 24h
91 of 182 checks
—
Tools
hidden behind auth
338 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add a2awire --transport http https://a2awire.com/mcp/http
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "a2awire": {
      "url": "https://a2awire.com/mcp/http"
    }
  }
}
~/.codex/config.toml
[mcp_servers.a2awire]
url = "https://a2awire.com/mcp/http"
.cursor/mcp.json
{
  "mcpServers": {
    "a2awire": {
      "url": "https://a2awire.com/mcp/http"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "a2awire": {
      "url": "https://a2awire.com/mcp/http"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://a2awire.com/mcp/http streamable-http needs key 336 ms 7 min ago
https://a2awire.com/mcp/sse sse answering 347 ms 7 min ago

A2AWire — questions

Answers built from our own checks of this server.

Why is there no tool list for A2AWire?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 50.0% of checks in the last 24 hours got a reply.
Is A2AWire working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 182 checks got a reply (50.0%), average response time 338 ms. The bar chart above shows every period we have measured.
Is A2AWire still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect A2AWire?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does A2AWire need an API key?
Yes. Every time we knock, A2AWire answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is A2AWire?
It answers our handshake in 338 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.