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

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 5 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
5 matching findings on this repo
  • low Old/deprecated-named symbol `certIssuerDNLegacy` in mcp/worker-configuration.d.…
  • low Old/deprecated-named symbol `looksLegacy` in mcpjam-inspector/client/src/compon…
  • low Old/deprecated-named symbol `seedOAuthLegacy` in mcpjam-inspector/client/src/li…
  • low Old/deprecated-named symbol `trimmedLegacy` in mcpjam-inspector/client/src/lib/…
  • low Old/deprecated-named symbol `prefersBorderLegacy` in mcpjam-inspector/server/ro…
View all legacy markers findings →
Commented-out code 245 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
12 matching findings on this repo
  • info Commented-code block (8 lines) in mcp/worker-configuration.d.ts:11495
  • info Commented-code block (6 lines) in soundcheck/src/app/api/release/dispatch/route…
  • info Commented-code block (8 lines) in mcpjam-inspector/vite.main.config.ts:50
  • info Commented-code block (6 lines) in mcpjam-inspector/client/vite.config.ts:14
  • info Commented-code block (6 lines) in mcpjam-inspector/client/vitest.config.ts:13
  • info Commented-code block (5 lines) in mcpjam-inspector/client/src/router.tsx:76
  • info Commented-code block (7 lines) in mcpjam-inspector/client/src/main.tsx:45
  • info Commented-code block (5 lines) in mcpjam-inspector/client/src/App.tsx:814
  • info Commented-code block (10 lines) in mcpjam-inspector/client/src/__tests__/App.ho…
  • info Commented-code block (6 lines) in mcpjam-inspector/client/src/stores/widget-deb…
  • info Commented-code block (5 lines) in mcpjam-inspector/client/src/stores/preference…
  • info Commented-code block (5 lines) in mcpjam-inspector/client/src/state/app-reducer…
View all commented-out code findings →
Config drift 47 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
12 matching findings on this repo
  • low File has no detected symbols: mcp/vite.config.ts
  • low File has no detected symbols: cli/tsup.config.ts
  • low File has no detected symbols: examples/chatgpt-apps/CoffeeShop/vite.config.ts
  • low File has no detected symbols: examples/conformance/basic/vitest.config.ts
  • low File has no detected symbols: examples/mcp-apps/express-react-template/vite.con…
  • low File has no detected symbols: examples/mcp-apps/reservation-app/vite.config.ts
  • low File has no detected symbols: examples/mcp-apps/sip-cocktails/vite.config.ts
  • low File has no detected symbols: examples/mcp-apps/flashcards-supabase/vite.config…
  • low File has no detected symbols: examples/evals/brightdata/vitest.config.ts
  • low File has no detected symbols: examples/evals/asana/jest.config.js
  • low File has no detected symbols: mcpjam-inspector/forge.config.ts
  • low File has no detected symbols: mcpjam-inspector/vite.preload.config.ts
View all config drift findings →
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.