shipmail-mcp
shipmail-mcp is an MCP server published by shipmail-to with verified support for the current MCP specification revision (2026-07-28). Last verified 2026-08-20.
Does shipmail-mcp support the current MCP specification (2026-07-28)?
Yes. shipmail-mcp has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-08-20).
Is shipmail-mcp a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for shipmail-mcp (as of 2026-08-20).
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.
Does shipmail-mcp support MCP revision 2026-07-28?
Yes. shipmail-mcp supports MCP revision 2026-07-28 (checked 2026-08-20).
When were shipmail-mcp's facts last verified?
2026-08-20. 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.
Which MCP spec revisions does shipmail-mcp support?
shipmail-mcp has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Supported | Source |
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.
Repository and package signals for shipmail-mcp
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 1
- Forks
- 0
- Last pushed
- (61 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Declared topics: agent-inbox, ai-agents, business-email, custom-domain-email, email, email-api, email-hosting, inbound-email, mcp, mcp-server, model-context-protocol, rest-api, shipmail, typescript, webhooks — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.7.3- Last published
- First published
- Releases
- 36
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 3
- Unpacked size
- 715 KB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· 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
- npm registry metadata for shipmail-mcp at published version 0.7.3, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/server, which resolves to @modelcontextprotocol/server@2.0.0 - accessed
- Published artifact of @modelcontextprotocol/server@2.0.0, retrieved 2026-08-20 - the artifact declares revision 2026-07-28 and implements the stateless server/discover method. Read from the artifact itself, not from release notes - accessed