Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo
107 of your 220 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 31.33s for a 56.0 MB repo slow.
  • Repobility's analysis ran in 19.77s after the clone landed.

MCPJam/inspector

https://github.com/MCPJam/inspector · scanned 2026-06-05 20:16 UTC (4 days, 14 hours ago) · 10 languages

1976 raw signals (198 security + 1778 graph) 11/13 scanners ran 41st percentile · Typescript · huge (>500K LoC) System graph score 60 (higher by 23)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 14 hours ago · v2 · 895 actionable findings from 2 signal sources. 191 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
70.7
/100
Security checks
81
66 findings
System graph
60
100.0% cov · 829 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 95.0 0.20 19.00
documentation_score 76.0 0.15 11.40
practices_score 77.0 0.15 11.55
code_quality 70.0 0.10 7.00
Overall 1.00 83.0
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 258 Medium 39 Low 205 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 66 System graph 829 Crowd 0 Layer: Quality 386 Security 14 Cicd 7 Software 58 Frontend 141 Hardware 2 Api 287

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Insecure pattern 'exec_used' in mcp/worker-configuration.d.ts:3016
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
mcp/worker-configuration.d.ts:3016
#2
`dangerouslySetInnerHTML` used in a React component — mcpjam-inspector/client/src/components/ui-playground/HandDrawnSendHint.tsx:73
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#3
`dangerouslySetInnerHTML` used in a React component — mcpjam-inspector/client/src/components/ui/chart.tsx:81
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#4
`dangerouslySetInnerHTML` used in a React component — mcpjam-inspector/client/src/components/ui/json-editor/json-editor-edit.tsx:658
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#5
Dangling fetch: POST /api/mcp/connect (cli/src/lib/inspector-api.ts:486)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#6
Dangling fetch: GET /api/mcp/servers (cli/src/lib/inspector-api.ts:494)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#7
Dangling fetch: POST /api/mcp/tools/list (cli/src/lib/inspector-api.ts:513)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#8
Dangling fetch: POST /api/mcp/tools/execute (cli/src/lib/inspector-api.ts:524)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#9
Dangling fetch: POST /api/mcp/tools/respond (cli/src/lib/inspector-api.ts:535)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#10
Dangling fetch: POST /api/release/dispatch (soundcheck/src/components/run-release.tsx:107)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/66da6397-b2ff-4a04-8b68-be2884660162/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/66da6397-b2ff-4a04-8b68-be2884660162/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.