{
  "markdown": "# inboxy — remote MCP server\n\n**Endpoint:** `https://mcp.inboxy.net` · **Transport:** Streamable HTTP · **Registry:** `net.inboxy/inboxy`\n\n[inboxy](https://inboxy.net) is a privacy-first email aliasing service with an\nAI-readable inbox. This server exposes your `@inboxy.net` mail, RSS feeds, and\naliases to any client that speaks the [Model Context Protocol](https://modelcontextprotocol.io),\nso an assistant can read, search, summarise, and reply to your mail without\never touching your real mailbox.\n\n> **This repository is documentation.** The server is hosted — there is nothing\n> here to install, build, or run, and no npm package to pull. It exists so the\n> registry listing has a home and so the connection details are versioned\n> somewhere public. The implementation is closed-source.\n\n## Connecting\n\nMost clients need only the URL. The server speaks OAuth 2.1 with Dynamic Client\nRegistration and PKCE, so interactive clients need no API key:\n\n```json\n{\n  \"mcpServers\": {\n    \"inboxy\": {\n      \"url\": \"https://mcp.inboxy.net\"\n    }\n  }\n}\n```\n\nClaude Desktop: **Settings → Developer → Edit Config**, paste the above,\nrestart, and sign in when redirected. Claude Code and other MCP clients take\nthe same URL and run the OAuth flow themselves.\n\n**Unattended agents** (OpenClaw, Hermes, Codex, CI) use a static bearer key\ninstead, minted under **Account → API keys**:\n\n```\nAuthorization: Bearer ik_…\n```\n\nKeys can be **address-scoped** to a single alias. A scoped key sees only that\nalias's mail, has its outbound `From:` pinned to it server-side, and is refused\nfor account-wide operations — so a leaked key exposes one alias, not the\naccount.\n\nFull setup, including the per-client config quirks that bite (OpenClaw's\n`--header` uses `Name=Value`, Hermes' YAML uses `Name: Value`), is at\n**https://inboxy.net/help/connect-mcp**.\n\n## What an agent can do\n\n48 tools as of v1.0.0, across eight groups, named `<group>_<action>` so\nclients render them under a common heading:\n\n| Group | Covers |\n|---|---|\n| `mail_*` | List, read, search, render, keep, delete, and send mail |\n| `outbox_*` | Inspect what the agent has sent |\n| `feed_*` | RSS subscriptions |\n| `article_*` | Articles within those feeds |\n| `address_*` | Mint and retire `@inboxy.net` aliases |\n| `account_*` | Plan, quota, rate limits, retention |\n| `digest_*` | Scheduled digest settings |\n| `mark_*` | Cross-domain bulk read-state |\n\nEvery tool declares an MCP behavioural annotation — read-only, idempotent, or\ndestructive — so clients can gate the destructive ones behind confirmation.\n\nThe canonical, always-current tool reference is\n**https://inboxy.net/help/connect-mcp** — deliberately not duplicated here, so\nit cannot drift.\n\n## What an agent can send\n\ninboxy gives your AI an inbox, not your Gmail. Every outbound path is scoped\nserver-side, so a leaked credential cannot become a spam cannon:\n\n| Tool | Recipient rule | Cap |\n|---|---|---|\n| `mail_reply` | Locked to the original sender of the message being replied to | 5/hour |\n| `mail_forward` | Locked to your own verified personal email | Idempotent |\n| `mail_send` | Any recipient, minus self-loops and reserved local-parts | Debits per-user send quota |\n| `mail_invite` | Any external address that isn't already an inboxy user | 10 per rolling 30 days |\n\nNo surface anywhere accepts a caller-supplied `From:`. Mail is always sent from\none of your own aliases, never from your real address.\n\n`@inboxy.net → @inboxy.net` mail is delivered in-network with no SMTP egress.\nAnything leaving the network carries a one-line `— inboxy.net — agentic email`\nattribution footer, injected at a single point so every send path behaves\nidentically.\n\n## Privacy\n\n- **EU data residency.** Storage and compute are pinned to Cloudflare's `eu`\n  jurisdiction.\n- **Scoped embeddings.** Semantic search runs on per-user vectors.\n- **90-day default retention** on message bodies; pinned messages are exempt.\n- **Short-lived tokens.** Refresh tokens rotate per OAuth 2.1 §4.3.1.\n- Revoke an OAuth grant under **Account → MCP / OAuth clients**, or a key under\n  **Account → API keys**. Revocation takes effect on the next request.\n\n[Privacy policy](https://inboxy.net/privacy) · [Terms](https://inboxy.net/terms)\n\n## Registry manifest\n\n[`server.json`](./server.json) is the manifest published to the official MCP\nregistry under `net.inboxy/inboxy`. Its `version` tracks the version this\nserver announces to clients on `initialize`.\n\n## Support\n\n`hello@inboxy.net` · Security disclosures: `security@inboxy.net`\n([security.txt](https://inboxy.net/.well-known/security.txt))\n\n## License\n\nThe contents of this repository are licensed Apache-2.0. See [LICENSE](./LICENSE).\n",
  "bytes": 4682,
  "sha": "5ce29c8dfcff2d30632b106f9430a08dd01dbf14d7494bb01ff987a993121ba2",
  "repo_slug": "inboxy/mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_net_inboxy_inboxy_557a8067/readme"
}