Github To Mcp
nirholas/github-to-mcpApache-2.0⭐ 17🔧 92 tools
C5.3SpiderScore (registry)
Decision
Allow with Risk
Confidence
90%
Github To Mcp has risks — usable with isolation (5.32/10, 0 critical, 0 high).
How This Was Decided
- positivew=0.5Overall quality score = 5.32/10 (grade C)
- negativew=0.3Tool description clarity score = 1.6/10
Source: SpiderRating automated security scanUpdated: 2026-03-22Protocol: v1.1
Description Quality
Composite: 1.6 / 10
3-Layer Breakdown
Description (38%)
1.6
Security (34%)
9.6
Metadata (28%)
5.1
Description Dimensions
Intent Clarity
1.5
Permission Scope
0.1
Side Effects
2.3
Capability Disclosure
2.9
Operational Boundaries
1.7
Category Ranking: Developer Tools
#13 of 30 · Top 43%Overall#135.3 (avg 3.9)
Security#59.6 (avg 8.4)
Description#271.6 (avg 3.1)
Metadata#285.1 (avg 6.8)
Why #13 in Developer Tools?
Top 43% of 30 toolsSecurity#59.6avg 8.4
Description#271.6avg 3.1
Metadata#285.1avg 6.8
How to reach #12? Need +0.0 overall to pass Mcp Gitlab Server (5.3). Biggest opportunity: Metadata is 1.7 below category average.
Top action: Add action verbs to 92 tool descriptions (e.g. 'Creates...', 'Deletes...') (+1.8)
Security Analysis
9.6
Score
0
Critical
0
High
0
Medium
0
Low
No security issues found.
Metadata Health
Provenance (40%)
7.0
Maintenance (35%)
4.0
Popularity (25%)
3.6
Badge
Add this badge to your README:
[](https://spiderrating.com/servers/nirholas/github-to-mcp)🛡️
Protect Your Agents
Get a free API key. Every MCP tool call checked against 15,923 rated servers in real-time.
Get Free API Key →📊
Monitor All Your Servers
Dashboard for your entire MCP portfolio. Score tracking, alerts, and compliance reports.
Start Free Trial →⭐
Scan Locally (Open Source)
Run SpiderShield on your own machine. 46+ security rules, zero data leaves your system.
Star on GitHub →