shipmail-mcp
Spec Support Unverified Confidence: Good (0.85)shipmail-mcp is an MCP server published by shipmail-to; its MCP spec-revision support has not been verified yet. Last verified 2026-08-07.
Does shipmail-mcp support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision shipmail-mcp supports (as of 2026-08-07).
Is shipmail-mcp a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for shipmail-mcp (as of 2026-08-07).
How do I connect to shipmail-mcp?
shipmail-mcp is available via a hosted remote endpoint at https://shipmail.to/api/mcp, the package npm:shipmail-mcp, the official MCP Registry under io.github.shipmail-to/shipmail-mcp, the source repository at https://github.com/shipmail-to/shipmail-mcp. Authentication: oauth. Transports: streamable-http.
When were shipmail-mcp's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
Shipmail MCP server for AI agent custom-domain email inboxes with REST API and webhooks.
How widely adopted is shipmail-mcp?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.shipmail-to/shipmail-mcp at version 0.7.3 - lists remote endpoint https://shipmail.to/api/mcp and repository https://github.com/shipmail-to/shipmail-mcp - accessed
- Endpoint probe of https://shipmail.to/api/mcp - authorization required (HTTP 401, Bearer realm="Shipmail API", resource_metadata="https://ship); capability set not observable without credentials - accessed