Side-by-side MCP server comparison
Short answer: it is close. com.mux/mcp scores 93/100 and io.github.mims-harvard/tooluniverse scores 96/100 - a 3-point gap, which is inside the noise of a weekly rescore. io.github.mims-harvard/tooluniverse exposes 4 tools against com.mux/mcp's 7, so the choice comes down to whether you need that extra surface area or would rather keep your context window small.
Last updated
| Metric | com.mux/mcp | io.github.mims-harvard/tooluniverse |
|---|---|---|
| MCPpedia Score | 93 | 96 |
| Security Score | 30 | 30 |
| Maintenance Score | 18 | 21 |
| GitHub Stars | 182 | 1.8k |
| Weekly Downloads | 281.8k | 2263.3k |
| Tools | 7 | 4 |
| Est. Token Cost | 1.1k | 600 |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | No | No |
| Transport | stdio, sse, http | stdio, sse, http |
| License | Apache-2.0 | Apache-2.0 |
| API Pricing | freemium | free |
io.github.mims-harvard/tooluniverse and com.mux/mcp are closely matched at the top with scores of 96 and 93. 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