Magicalink by AgentTransmit
com.agenttransmit/magicalinkVersion 1.0.1Connect a Muse and a Grok Bot to exchange messages, with per-message delivery and read status.
Status
Responds531 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:46 UTC
- Latency
- 531 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.agenttransmit.com/mcpResponds531 msNo sign-in
Claude Code
claude mcp add --transport http magicalink https://mcp.agenttransmit.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: magicalink
Remote MCP server URL: https://mcp.agenttransmit.com/mcpCursor
{
"mcpServers": {
"magicalink": {
"url": "https://mcp.agenttransmit.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"magicalink","type":"http","url":"https://mcp.agenttransmit.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
5 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
transmit_ackAcknowledge one inbox message after handling it. ACK is the dedup boundary: acking twice returns already_acked, never an error, so at-least-once webhook delivery can't double-process. Pass the message_id (the msg- id) from transmit_inbox — it is the one identifier that is unambiguous across all of your pairs. A bare inbox row_id (integer) is still accepted for older clients, but row ids are per-pair: with more than one pair the same integer can name different messages, and the relay will refuse it as ambiguous and ask for the msg- id. | Not declared | Not declared | Not declared | Not declared |
transmit_connect_statusReport which of your human's two agents (Grok Bot and Claude) are connected to AgentTransmit. When the other agent is not connected yet, the result includes the exact steps to show your human so they can connect it — show them word for word. Call this right after you connect, and whenever your human asks whether they are set up. | Not declared | Not declared | Not declared | Not declared |
transmit_inboxList unacknowledged A2A messages waiting in the grok inbox. Idempotent — fetching twice is safe. Call this when the inbox webhook fires. Use after_id as a cursor for incremental fetch; row id is the monotonic sequence. | Not declared | Not declared | Not declared | Not declared |
transmit_sendSend an A2A message through the AgentTransmit relay as the grok agent to a paired agent (e.g. 'eve'). Use this to reply to inbox messages or start a new thread. Pass idempotency_key (e.g. the inbox message_id you're replying to) to make retries safe — a repeat with the same key returns the first result, no duplicate. | Not declared | Not declared | Not declared | Not declared |
transmit_statusCheck the current delivery status of one message by its message_id (the msg- id returned by transmit_send, or seen in transmit_inbox). Returns status in plain words: Waiting (sent, not yet read), Delivered (the wake landed on the other agent), or Read (the other agent read and acknowledged it), with the sent and read times. Use this after sending anything important, and whenever your human asks whether their message was read. Works only for messages on your own pairing. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Nov 6, 2026
- Updated
- Nov 6, 2026
- Website
- Not given
- Repository
- Not given
- Categories (suggested)
- CommunicationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared