The External Brain for AI Coding Agents — see what your LLM can't see. Provides instant, structured intelligence about your entire codebase without reading files into the AI's context window.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"blindspot-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Blindspot MCP Blindspot is a local, general-purpose context engine for AI coding agents. It exists for one job: - help the agent understand a project - help the agent understand symbols and relationships - help the agent estimate change impact before editing - do this across different languages and project layouts Blindspot is intentionally small. It is not trying to be a deployment system, policy engine, rollout manager, or autonomous edit platform. ## Why Most agents can edit files, search text, and run commands. What they usually lack is a compact, reusable understanding layer for: - project structure - symbol ownership - callers and references - inheritance and composition - likely blast radius of a change That is the gap Blindspot fills. Paid context engines already proved this model is useful. Blindspot is the local and reusable alternative. ## Design Goals - Small MCP surface - Works across languages and frameworks - Gives structured context instead of file dumps - Helps any agent write better code with fewer blind edits - Stays useful even when framework-specific intelligence is missing ## Language Coverage Blindspot keeps one public API and improves the engine underneath it. - Strong support: Python, PHP, JavaScript, TypeScript, Go - Solid project-structure and syntax-aware support: Dart / Flutter, React Native, Node.js - Additional generic support: Java, Kotlin, C#, Ruby, Rust, mixed repos The contract does not change per language. `get_context(...)` stays the same; only the quality of the internal enrichment improves. ## Core Tools Blindspot now exposes only the core context-engine surface: - `set_project_path`: call once to bind Blindspot to the repo - `get_project_snapshot`: one-shot repo overview at session start - `get_context`: main entrypoint for file, symbol, relationship, and impact context - `get_symbol_body`: exact symbol metadata or bounded source excerpt - `get_edit_region`: small numbered excerpt around a symbol or line r…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.