Side-by-side MCP server comparison
Short answer: it is close. io.github.Atomic-Mail/mcp scores 94/100 and Resend MCP scores 91/100 — a 3-point gap, which is inside the noise of a weekly rescore. io.github.Atomic-Mail/mcp exposes 1 tools against Resend MCP's 29, so the choice comes down to whether you need that extra surface area or would rather keep your context window small.
Last updated
| Metric | io.github.Atomic-Mail/mcp | Resend Mcp |
|---|---|---|
| MCPpedia Score | 94 | 91 |
| Security Score | 29 | 30 |
| Maintenance Score | 20 | 20 |
| GitHub Stars | 267 | 565 |
| Weekly Downloads | 15476.0k | 168287.9k |
| Tools | 1 | 29 |
| Est. Token Cost | 150 | 4.3k |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | No | Yes |
| Transport | stdio, sse, http | stdio, sse, http |
| License | MIT | MIT |
| API Pricing | freemium | freemium |
io.github.Atomic-Mail/mcp and Resend Mcp are closely matched at the top with scores of 94 and 91. Resend Mcp edges ahead on security. Check each server's detail page to decide which fits your use case.
Compare up to 4 servers: mcppedia.org/compare/server-a-vs-server-b-vs-server-c