Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Codebase Brain

PYPI · CODEBASE-BRAIN-MCP

Cited, searchable memory of a codebase: hybrid search, git history, impact analysis, doc drift.

Available components

−11 this week 74 Trust /100

Last scanned (16 hours ago)

Scores higher than 67% of PyPI servers

Category Code Search and Documentation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security49
  • Malware scan not yet available for this package.Unverified
  • Known CVEs were checked across the 69 of 71 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 69 of 71 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Nomannazir/codebase-brain-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 14 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1453 tokens (~145/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 10 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/codebase-brain-mcp@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Nomannazir/codebase-brain-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Nomannazir/codebase-brain-mcp/.github/workflows/release.yml@refs/tags/v0.2.1
Rekor log index 3732163537
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:a6511059c13870067848a794b7ea5db95187e6e5cfb9e1bed972eeef1ff7936a

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool uv_build

Background: Why install scripts are a supply-chain risk →

Dependencies 69 packages
Packages resolved 69
Stale 8
No linked repository 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,309 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ask_codebase ~146

Gather the code and docs most relevant to a question, plus related commits, as numbered, cited sources. Use this to answer "how does X work?" or "where is Y handled?" questions. Answer from these sources only and cite each claim as path:start-end; open a source in full with read_lines. For filters, use search.

NameTypeReqDescription
kinteger–How many results to return, 1 to 25.
questionstringyesA question in plain words, e.g. "How are sessions expired?"
repo––Name of an indexed repo, as list_repos shows it. Leave out when only one repo is indexed.
NameTypeReqDescription
instructionsstringyes–
questionstringyes–
related_commitsarrayyesCommits whose messages match the question.
repostringyes–
sourcesarrayyes–

No examples provided.

explain_history ~206

Why code looks the way it does. Use this before removing or rewriting code that looks odd, or to answer "why is it like this?". Give a symbol, or a path with an optional line range. Returns who wrote the current lines, every commit that changed them (with the relevant diff), and the title and description of the pull request behind each commit (GitHub only).

NameTypeReqDescription
end_line––Last line of the range (with path).
max_commitsinteger–How many commits to return, newest first.
path––A file in the repo. Narrow it with start_line and end_line.
repo––Name of an indexed repo, as list_repos shows it. Leave out when only one repo is indexed.
start_line––First line of the range (with path).
symbol––A function, class or method, e.g. "unsign" or "Signer.sign". Use this or path.
NameTypeReqDescription
authorshiparrayyes–
changesarrayyesCommits that changed these lines, newest first.
citationstringyes–
instructionsstringyes–
pull_requestsarrayyes–
repostringyes–
symbol–yes–

No examples provided.

find_doc_drift ~179

Documentation that no longer matches the code. Use this to check a README or docs folder, or before a release. Finds files, functions, settings and flags that don't exist; code examples that pass parameters a function doesn't take; imports that would fail; and stale sections. Each finding has a severity, cites the doc section and suggests a fix. Changelogs are skipped.

NameTypeReqDescription
check_historyboolean–Also flag doc sections last edited long before the code they describe.
limitinteger–Most findings to return, 1 to 200, most severe first.
path_prefix––Only consider files under this path, e.g. "src/auth/" or "docs/".
repo––Name of an indexed repo, as list_repos shows it. Leave out when only one repo is indexed.
NameTypeReqDescription
findingsarrayyes–
references_checkedintegeryes–
repostringyes–
sections_checkedintegeryes–
summarystringyes–

No examples provided.

impact_of_change ~174

What breaks if a symbol changes: code that uses it directly, code that uses that code, and the tests involved. Use this before editing a shared function, and run or update the tests it lists. Python, JavaScript and TypeScript are analysed structurally. Matches are by name, so check the same-name notes it returns.

NameTypeReqDescription
depthinteger–1 = direct users only; 2 or 3 also follows users of those users.
path––The file that defines symbol, when several files define that name.
repo––Name of an indexed repo, as list_repos shows it. Leave out when only one repo is indexed.
symbolstringyesThe function, class or method you plan to change, e.g. "discount" or "Cart.total".
NameTypeReqDescription
directarrayyes–
indirectarrayyes–
notesarrayyes–
same_name_definitionsarrayyes–
summarystringyes–
symbolstringyes–
targetstringyespath:start-end of the definition analysed.
testsarrayyesCitations of tests that exercise the target, directly or not.

No examples provided.

index_repo ~119

Index a repository so the other tools can search it. Use this first, and again after the code changes: re-running only re-embeds files whose content changed. A URL is cloned with full history (blobless), so explain_history works. Reports progress while it runs, and returns file counts and the commit indexed.

NameTypeReqDescription
name––Name to index it under. Defaults to the folder or repository name.
sourcestringyesA local directory, or an https git URL such as https://github.com/owner/repo.
NameTypeReqDescription
chunks_totalintegeryes–
commit–yes–
commits_addedintegeryes–
commits_totalintegeryes–
files_indexedintegeryesFiles embedded this run (new or changed).
files_removedintegeryes–
files_seenintegeryes–
files_unchangedintegeryes–
full_rebuildbooleanyes–
repostringyes–
rootstringyes–
secondsnumberyes–

No examples provided.

list_repos ~46

Repositories indexed so far, with their size, languages and the commit they were indexed at. Use this first to see what's available and to get the repo names the other tools take.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

read_lines ~124

Exact, numbered lines from a file in an indexed repo. Use this to open a citation in full before quoting or editing it, since search results are trimmed snippets. Refuses paths outside the repo.

NameTypeReqDescription
endintegeryesLast line to return (inclusive).
pathstringyesThe file, relative to the repo root, as a citation shows it.
repo––Name of an indexed repo, as list_repos shows it. Leave out when only one repo is indexed.
startintegeryesFirst line to return (1-based).
NameTypeReqDescription
resultstringyes–

No examples provided.

search ~195

Hybrid search over code and docs (BM25 keywords plus local embeddings, fused by rank). Use this for a targeted lookup, or when you need filters by folder or chunk kind; for a question you'll answer in prose, use ask_codebase instead. Returns ranked chunks, each with a path:start-end citation, its symbol and a snippet.

NameTypeReqDescription
kinteger–How many results to return, 1 to 25.
kinds––Only these chunk kinds: function, class, method, interface, type, enum, module, section (docs) or code (other files).
path_prefix––Only consider files under this path, e.g. "src/auth/" or "docs/".
querystringyesAn identifier (normalizeRetryOptions) or plain words.
repo––Name of an indexed repo, as list_repos shows it. Leave out when only one repo is indexed.
NameTypeReqDescription
querystringyes–
repostringyes–
resultsarrayyes–

No examples provided.

search_history ~120

Find commits by what their messages say. Use this to answer "when did we change X?" or "which commit fixed Y?". For the history of one function or file, use explain_history instead.

NameTypeReqDescription
kinteger–How many results to return, 1 to 25.
querystringyesWords from commit messages, e.g. "fix timezone" or "drop python 3.8".
repo––Name of an indexed repo, as list_repos shows it. Leave out when only one repo is indexed.
NameTypeReqDescription
resultarrayyes–

No examples provided.

Install

How do I install the Codebase Brain MCP server?

Codebase Brain runs locally as a PyPI package, launched with uvx codebase-brain-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · codebase-brain-mcp

# add to Claude Code
claude mcp add nomannazir-codebase-brain-mcp -- uvx codebase-brain-mcp
Common questions

What is the Codebase Brain MCP server?

Codebase Brain is an MCP server listed in the public MCP registry as io.github.Nomannazir/codebase-brain-mcp. Cited, searchable memory of a codebase: hybrid search, git history, impact analysis, doc drift. This page covers its PyPI package (codebase-brain-mcp).

Is the Codebase Brain MCP server safe to use?

Codebase Brain scores 74 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Codebase Brain MCP server expose?

Codebase Brain exposes 9 tools: index_repo, search, ask_codebase, explain_history, impact_of_change, and 4 more. Their descriptions and schemas cost roughly 1,309 tokens of context every time the server is loaded.

Is the Codebase Brain MCP server still maintained?

Codebase Brain is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Codebase Brain MCP server under?

Codebase Brain declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Codebase Brain MCP server?

VerifyMCP ran 15 checks on Codebase Brain, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Codebase Brain: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.