Blindspot MCP
Related Servers
Alternatives to Blindspot MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA graph-powered code intelligence engine that indexes codebases into a structural knowledge graph to provide AI agents with deep context on function calls, types, and execution flows. It offers local, zero-dependency tools for hybrid search, impact analysis, and dead code detection across Python, JavaScript, and TypeScript projects.885 PyPI814MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to retrieve precise, real-time architectural context—such as domains, models, routes, and events—from a codebase, avoiding the need to dump entire files into prompts.15 npm1MIT
- AlicenseNot gradedqualityAmaintenanceA local code-intelligence engine for AI agents that indexes repositories into a PostgreSQL-backed code graph and serves structured, token-budgeted context over MCP and HTTP, enabling targeted queries on symbols, dependencies, contracts, and impact analysis.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal-first cross-service code intelligence engine for AI agents, connecting frontend, gateways, backend services, and databases to enable impact analysis and change planning.Apache 2.0
- AlicenseAqualityBmaintenanceGives coding agents structural understanding of a codebase: it indexes Java and Python repositories to resolve symbols, call sites with confidence tiers, module dependencies, diff impact, and hotspots. It also ships an eval harness that measures whether this context actually helps an agent.8MIT
- FlicenseNot gradedqualityDmaintenanceA minimalist indexing tool that provides AI agents with semantic search and structural AST parsing for deep codebase understanding. It enables autonomous agents to navigate large codebases predictably using vector embeddings and native language server capabilities like definition and reference tracking.-
TDQS
Scored across 9 tools
Each tool has a distinct purpose: initialization, index building, file discovery, context retrieval, symbol extraction, edit region extraction, overview, search fallback, and path setting. No two tools appear to do the same thing, minimizing ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., build_deep_index, get_context, set_project_path). No mixing of naming conventions, which aids predictability.
With 9 tools, the server covers essential operations for code analysis and edit preparation without being bloated. Each tool earns its place, and the scope is well-defined.
The tool set covers project initialization, index management, file discovery, context retrieval, symbol detail, edit regions, and project overview. Minor gaps like a path-switching tool or direct edit application are absent, but the primary focus on analysis and context is well-served.