Side-by-side MCP server comparison
Short answer: it is close. io.github.mims-harvard/tooluniverse scores 96/100 and Modelcontextprotocol scores 96/100 - a 0-point gap, which is inside the noise of a weekly rescore. they are close enough on every measure that the deciding factor is which upstream service you already use.
Last updated
| Metric | io.github.mims-harvard/tooluniverse | Modelcontextprotocol |
|---|---|---|
| MCPpedia Score | 96 | 96 |
| Security Score | 30 | 30 |
| Maintenance Score | 21 | 21 |
| GitHub Stars | 1.8k | 2.6k |
| Weekly Downloads | 2263.3k | 9.4k |
| Tools | 4 | 4 |
| Est. Token Cost | 600 | 600 |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | No | No |
| Transport | stdio, sse, http | stdio, http |
| License | Apache-2.0 | MIT |
| API Pricing | free | freemium |
io.github.mims-harvard/tooluniverse and Modelcontextprotocol are closely matched at the top with scores of 96 and 96. 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