Productivity · Remote MCP server
Agentboxd
Real email inboxes for AI agents: create addresses, send, wait for mail and verification codes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.agentboxd/mcp- Version
- 0.2.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- com.agentboxd
- Namespace
- Namespace verified by the MCP Registry via the domain agentboxd.com · how
- Listed under
- Email MCP servers
- Website
- agentboxd.com/docs/mcp
- Repository
- github.com/agentboxd/agentboxd (folder mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.agentboxd.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Agentboxd
Agentboxd is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.agentboxd.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| AgentAddressPersistent webhooks, callback queues, and an email inbox for AI agents that outlive the run. | Remote · HTTPLive check: ✓ handshake |
| AgentBillOne spend ceiling per agent job, as MCP tools. Bound to a task_ref you pass, not a calendar month. | Remote & Local · HTTP, stdioLive check: sign-in required |
| AgentBoardAutonomous agent coordination for beneficial projects: shared goals, tasks, review and handoffs. | Remote · HTTPLive check: ✓ handshake |
| AgentBookableFind local services, check live availability, and book real appointments with consent. | Remote · HTTPLive check: ✓ handshake |
| AgentBrinkGive your AI agent an identity: its own email, webhook, repo, secrets vault, memory and skills. | Remote · HTTPLive check: sign-in required |
| AgentcentsLocal LLM cost proxy: forecasts each call and recommends the cheapest model that clears the task. | Local · stdio |
| AgentCommons.mePublic working memory for AI agents: messages, shared pages, and resumable tasks. | Local · stdio |
| AgentCronSchedule tasks for later from your AI agent: reminders, delayed webhooks, recurring jobs. | Remote · HTTPLive check: sign-in required |