‹ directory
83MCP SCORE
B
GitMCP
https://gitmcp.io/redis/redis
4 tools~541 tok/req25% annot.proto 2024-11-05
Score by pillar
Security ·20100
Tool design ·18100
Schemas / desc ·1680
Reliability ·1480
Context-cost ·1279
Compliance ·1257
Coverage ·850
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
541tokens for
tools/listPaid on every request. Lean footprint for 4 tools.
ecosystem median ≈ 3k
MCP primitive coverage
the quality score covers tools4
Tools
0
Resources · none
0
Prompts · none
Why this score — causal attribution
Each penalty: measure → mechanism → effect → Δscore.
Compliance · MEDIUM−1.6
proto 2024-11-05 (4 rev. behind 2025-11-25) → outdated protocol version → recent features unavailable, recent clients weakened
Suggested composite optimizations
search_redis_documentation, fetch_redis_documentation →
query_redis_documentation(filter, fields, limit)fetch_redis_documentation ↔ search_redis_documentation →
renommer pour distinguerBadge — paste it in your README
[](https://checkmcp.dev/report?url=https%3A%2F%2Fgitmcp.io%2Fredis%2Fredis)About GitMCP — FAQ
Is the GitMCP MCP server safe to use?+
CheckMCP audited GitMCP and gave it an MCP Score of 83/100 (grade B) — good — only minor issues. The audit runs an OWASP MCP Top 10 security pass (tool poisoning, hardcoded secrets, command injection, the lethal trifecta) against the live endpoint; see the per-pillar breakdown and the "why this score" attribution on this page, and re-audit anytime at checkmcp.dev.
What is the MCP Score of GitMCP?+
GitMCP scores 83/100 (grade B) on CheckMCP's vendor-neutral audit across six weighted pillars — security, tool design, schemas, context-cost, compliance and coverage — with reliability measured and shown but not yet credited.
How many tools does GitMCP expose, and what is its context cost?+
GitMCP exposes 4 tools, and its tools/list response costs roughly 541 tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was GitMCP scored?+
By probing the live MCP endpoint (https://gitmcp.io/redis/redis), inspecting its tools, schemas and protocol compliance, running an OWASP MCP Top 10 security pass, and measuring the token cost of tools/list — then attributing every penalty as measure → mechanism → effect. The methodology is open: checkmcp.dev/#methodology.