Side-by-side MCP server comparison
Short answer: pick com.luthersystems.insideout/mcp. It scores 90/100 to io.github.RedHold/diagrams-so-mcp's 85/100, and it exposes 8 tools to io.github.RedHold/diagrams-so-mcp's 4. io.github.RedHold/diagrams-so-mcp is still worth a look if you are already invested in it - the full breakdown below shows exactly where the 5 points go.
Last updated
| Metric | com.luthersystems.insideout/mcp | io.github.RedHold/diagrams-so-mcp |
|---|---|---|
| MCPpedia Score | 90 | 85 |
| Security Score | 30 | 30 |
| Maintenance Score | 15 | 10 |
| GitHub Stars | 0 | 0 |
| Weekly Downloads | 2263.3k | 85 |
| Tools | 8 | 4 |
| Est. Token Cost | 1.2k | 600 |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | No | No |
| Transport | http, stdio | stdio, sse, http |
| License | Apache-2.0 | Apache-2.0 |
| API Pricing | unknown | freemium |
com.luthersystems.insideout/mcp leads with a score of 90 (A), ahead of io.github.RedHold/diagrams-so-mcp's 85 (A).
Compare up to 4 servers: mcppedia.org/compare/server-a-vs-server-b-vs-server-c