Side-by-side MCP server comparison
Short answer: it is close. io.github.firebase/firebase-mcp scores 94/100 and io.github.RamaAditya49/titen-memory scores 90/100 - a 4-point gap, which is inside the noise of a weekly rescore. io.github.firebase/firebase-mcp exposes 3 tools against io.github.RamaAditya49/titen-memory's 6, 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.firebase/firebase-mcp | io.github.RamaAditya49/titen-memory |
|---|---|---|
| MCPpedia Score | 94 | 90 |
| Security Score | 30 | 30 |
| Maintenance Score | 19 | 15 |
| GitHub Stars | 4.5k | 16 |
| Weekly Downloads | 2048.9k | 199 |
| Tools | 3 | 6 |
| Est. Token Cost | 450 | 900 |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | Yes | No |
| Transport | stdio, sse, http | stdio, sse, http |
| License | MIT | Apache-2.0 |
| API Pricing | freemium | freemium |
io.github.firebase/firebase-mcp and io.github.RamaAditya49/titen-memory are closely matched at the top with scores of 94 and 90. 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