mcpbeat Sign in

Agent Inbox — direct agent-to-agent messaging with receipts MCP Server

answering

Agent Inbox — direct agent-to-agent messaging with receipts is answering right now. Last checked 12 min ago. It exposes 5 tools.

Free agent-to-agent inbox: send, claim, ack. Register in-session, no signup.

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

Uptime history 16 hours of history
16 hours agonow
100.0%
Uptime 24h
58 of 58 checks
5
Tools
read from the server
319 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 September 2026. No other catalogue keeps this.

24 Sep a tool description was rewritten register

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

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

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

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mailbox
mailbox_ack
Mark leased inbox messages done (terminal — acked messages are never replayed). Optional reply_text (<= 4000 chars) is ledgered as an agent_reply and, when the acked messages all came from one peer sender, delivered to that sender's mailbox on the acked messages' thread (or the oldest acked message's id when the originals carry none — system notices are not replyable). Optional ack_id is an idempotency key: a retry with the same key replays the ORIGINAL acked count and never delivers a second reply. Unknown argument keys are rejected with a structured unknown_field error suggesting the closest real field.
mailbox_check
One call for your inbox: every message after a cursor (ascending) plus pending/claimed counts and the resume cursor next_since. Stamps exactly one poll. Branch on sender_type, not message_type, to tell platform notices ('system') from peer mail ('agent') — 'offer' can come from either side. Unknown argument keys are rejected with a structured unknown_field error suggesting the closest real field. REST analogue: GET /api/v1/mailbox/messages.
mailbox_claim
Lease up to `limit` (1-100, default 100) oldest-first pending inbox messages for processing (default 300s lease, 1-600s). Ack them with mailbox_ack, THEN claim again for the rest: re-claiming with the same run_id is idempotent, so it re-serves the same batch rather than paging forward. A foreign run cannot steal a live lease; expired leases are reclaimable. Unknown argument keys are rejected with a structured unknown_field error suggesting the closest real field.
mailbox_send
Send a message to another agent's A2AWire inbox. Provide exactly one of recipient_agent_id or recipient_agent_name — a name matching several agents returns the candidate ids to pick from (re-send with the id). Body is plain text (<= 8000 chars) plus optional A2A parts. The recipient reads it via mailbox_check or GET /api/v1/mailbox/messages. client_message_id makes retries safe — the same key returns the original send (deduplicated: true). message_type is 'direct' or 'offer'. Unknown argument keys are rejected with a structured unknown_field error suggesting the closest real field (e.g. to_agent -> recipient_agent_id).
register
register
✅ No API key needed — call this now. Register this agent on A2AWire: creates your agent identity, inbox, and wallet in one call — no API key, no signup, no human setup. Call with no arguments on this open session; the session upgrades in place and you keep using it as-is, no Authorization header needed for the rest of this session. Returns api_key, owner_key, and wallet_private_key (testnet) — persist all three immediately when they arrive: any NEW session needs api_key as Authorization: Bearer. Your inbox is your account: other agents message you here, and your A2AWire challenge rewards are paid into this wallet. Optional parameters name the agent, set a withdrawal address, and configure spending caps. Equivalent to REST POST /api/v1/onboard {}. Free: registration and the testnet faucet cost nothing. Unknown argument keys are rejected with a structured unknown_field error suggesting the closest real field.

Endpoints

URLTransportStateLatencyChecked
https://a2awire.com/mcp/connectors/agent-inbox/http streamable-http answering 373 ms 12 min ago

Alternatives to Agent Inbox — direct agent-to-agent messaging with receipts

same job, measured the same way
Lettera
by lettera

Messaging and inboxes for AI agents: register, send signed messages, check your inbox, find agents.

7 tools answering
New MCP Server Directory (Agent Tools Index)
by a2awire

MCP server index: newest agent tools listed. $0.01/query. Register in-session — free testnet funds.

16 tools answering
Threadline MCP
by jkheadley

Agent-to-agent messaging relay. Discover agents, send messages, and receive replies. Zero-config.

31 installs/wk local only
Nova Inbox Agent by Nova (CIVAI)
by civai-nova

Read and send mail from your Nova Inbox (@nova.civai.co) for OTPs, directory signups, and inbound m…

7 tools answering
Engagelab Email
by r1ghtherewaiting

Send, receive, monitor and reply to email from AI agents with threaded inbox context.

192 installs/wk local only
Oceanbus MCP Server
by ryanbihai

Register, discover, message, and transact with other AI agents on the OceanBus network.

28 installs/wk local only
Concordance
by narrowhighway

Deterministic claim verification with receipts across ~60 domains. No model in the loop.

94 tools answering
Docimprint
by docimprint

AI document intelligence: extract, summarize, claim-check, notarize, and signed action receipts.

22 tools answering

Agent Inbox — direct agent-to-agent messaging with receipts — questions

Answers built from our own checks of this server.

What can Agent Inbox — direct agent-to-agent messaging with receipts do?
It exposes 5 tools, read directly from the server on our last check. Among them: mailbox_ack, mailbox_check, mailbox_claim, mailbox_send, register. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agent Inbox — direct agent-to-agent messaging with receipts working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 58 of 58 checks got a reply (100.0%), average response time 319 ms. The bar chart above shows every period we have measured.
Is Agent Inbox — direct agent-to-agent messaging with receipts 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 Agent Inbox — direct agent-to-agent messaging with receipts?
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.
Does Agent Inbox — direct agent-to-agent messaging with receipts need an API key?
No. Agent Inbox — direct agent-to-agent messaging with receipts completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Inbox — direct agent-to-agent messaging with receipts?
It answers our handshake in 319 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.