spider-map
MCP server that analyzes codebases to provide dependency graphs, impact analysis, and file insights across 15+ programming languages, enabling AI assistants to understand project structure and navigate code efficiently.
Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
rofid-c
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
configure_auto_indexingConfigure and start auto-indexing service with file watcher and 3-second debounce.
get_project_mapGenerate or load the cached codebase dependency graph (Spider Map). Supports multiple response modes for token optimization.
get_file_infoGet detailed info about a specific file: dependencies, dependents, metrics, and impact analysis. Very token-efficient (98% reduction).
simulate_impactSimulate a change in a specific file to see which other files will be directly or indirectly affected (Blast Radius Analysis).
search_filesFind files by criteria such as file type, risk level, role, or dependency count. Returns filtered file list for efficient querying.
get_code_metricsGet code metrics for files: complexity, lines of code, test coverage, function count, etc. Useful for refactoring decisions.
detect_changesDetect which files have changed since the last crawl. Useful for understanding code evolution and testing impact.
get_time_analysis4D Time-series analysis: track complexity evolution, predict hotspots, analyze patterns over time. Provides historical insights for informed decisions.
predict_hotspotsPredict files likely to become problematic based on historical trends, complexity growth, and change patterns. Helps prevent technical debt.
query_temporalAdvanced temporal queries: search by trend, volatility, velocity, or patterns with confidence scores.
analyze_evolutionComprehensive evolution analytics: complexity trends, stability analysis, hotspot evolution, patterns, and recommendations.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
launch-editor vulnerable to command injection via the crafted request on Windows
vite: `server.fs.deny` bypass on Windows alternate paths
Vite has an `server.fs.deny` bypass with an invalid `request-target`
Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling
PROJECT_ROOTTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
11/11 tools missing one or more hints — configure_auto_indexing (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_project_map (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_file_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool test coverage
Only 0/11 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
Readable source code
3 files are minified or bundled, which is usually build output rather than concealment
Ship unminified, readable source.
Production dependencies are patched
0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.1 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dev dependencies
2 critical/high in dev-only deps (does not ship to users)
Upgrade dev dependencies when convenient.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/rofid-c/codebase-analyzer-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check