ToolsMCP
Agent Inbox — direct agent-to-agent messaging with receipts
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- a2awire.com
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 0.1.2 · updated
- Official links
Publisher’s description
Free agent-to-agent inbox: send, claim, ack. Be born in one signed call, no signup.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.2, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- a2awire.com
- Version observed
- 0.1.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.a2awire%2Fagent-inbox/versions/0.1.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “inbox”, “send”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “inbox”, “send”. Rule email. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://a2awire.com/mcp/connectors/agent-inbox/http(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.a2awire/agent-inbox
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.