Developer · Remote MCP server
Brain Scanner
Codebase graphs, caller impact analysis, and recorded project context for AI coding agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.kevin-lozada-santos/brain-scanner- Version
- 0.7.7
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-12
- Updated
- 2026-09-12
- Publisher
- kevin-lozada-santos (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/kevin-lozada-santos) · how
- Website
- brainscanner.dev/connect
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://brainscanner.dev/mcp/v2 | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Brain Scanner
Brain Scanner is a remote MCP server: there is nothing to install. Its endpoint is https://brainscanner.dev/mcp/v2, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| BoyceDeterministic SQL compiler for AI agents. Your agent stops guessing SQL. | Local · stdio |
| Br8nCapture dev context on interrupt; replay it as a 30-second resume card. Git stash for your head. | Local · stdio |
| brain - the recorderRecords your Claude Code, Codex and Pi history before deletion. Cited-or-abstain recall. | Local · stdio |
| Brain ProtocolVerifiable Memory for AI Agents - knowledge graph, FTS, Starknet proofs, local or cloud. | Local · stdio |
| BrainboxPersistent, portable memory for AI assistants - your private memory graph, from any MCP client. | Remote · HTTPLive check: sign-in required |
| brainCloud MCP HelperHelper for brainCloud MCP that gives it local file access, enabling easy git sync of cloud code. | Local · stdio |
| BrainfeatherLong-term memory for AI coding agents: durable project facts, recalled by every MCP client. | Remote & Local · HTTP, stdioLive check: sign-in required |
| BrainfileBrainfile memory layer for Claude Code over MCP: free starter files + weekly freshness feed. | Remote · HTTPLive check: ✓ handshake |