Side-by-side MCP server comparison
Short answer: pick io.github.Atomic-Mail/mcp. It scores 94/100 to io.github.Maxim-Mazurok/teams-api's 87/100, and it has 267 GitHub stars against 5. io.github.Maxim-Mazurok/teams-api is still worth a look if you are already invested in it — the full breakdown below shows exactly where the 7 points go.
Last updated
| Metric | io.github.Atomic-Mail/mcp | io.github.Maxim-Mazurok/teams-api |
|---|---|---|
| MCPpedia Score | 94 | 87 |
| Security Score | 29 | 30 |
| Maintenance Score | 20 | 12 |
| GitHub Stars | 267 | 5 |
| Weekly Downloads | 15476.0k | 336 |
| Tools | 1 | 2 |
| Est. Token Cost | 150 | 300 |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | No | Yes |
| Transport | stdio, sse, http | stdio, http |
| License | MIT | MIT |
| API Pricing | freemium | freemium |
io.github.Atomic-Mail/mcp leads with a score of 94 (A), ahead of io.github.Maxim-Mazurok/teams-api's 87 (A).
Compare up to 4 servers: mcppedia.org/compare/server-a-vs-server-b-vs-server-c