Project Brain
OCI · GHCR.IO/GENTLEELEPHANT/PROJECT-BRAIN:V2.0.3
Read-only source search and retrieval across configured GitHub repositories
Available components
Last scanned (21 hours ago)
Scores higher than 74% of OCI servers
Category Code Search and Documentation
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 68 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 706 tokens (~117/item across 6 items; 6 tools + 0 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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −3
- Stability: pass → 0.80 functional
- 12 Oct 26 +1
- Stability: 0.93 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 −3
- Stability: pass → 0.80 functional
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 16 Oct 2026 · Analysed oci/ghcr.io/gentleelephant/project-brain:v2.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
project_code_files ~123
List tracked file paths at the current prepared revision of one or more repositories. Optional pathPrefix narrows to a directory; optional query filters file names. File locations are navigation hints; read relevant lines before citing a claim.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | maximum file paths, from 1 to 500 |
| pathPrefix | string | – | optional repository-relative directory prefix |
| query | string | – | optional case-insensitive text contained in the file path |
| repos | null|array | – | optional repository slugs (owner/repo); defaults to all configured repositories |
No output schema declared.
No examples provided.
project_code_read ~107
Read a narrow repository-relative source range from one repository, limited to 300 lines. The repository is cloned or refreshed on demand; the result includes the prepared revision and a citation.
| Name | Type | Req | Description |
|---|---|---|---|
| endLine | integer | – | last line, defaults to 200 and at most 300 lines per call |
| path | string | yes | repository-relative file path |
| repo | string | yes | repository slug (owner/repo) |
| startLine | integer | – | first line, defaults to 1 |
No output schema declared.
No examples provided.
project_code_search ~146
Search exact text (or a regular expression) across one or more configured repositories. Repositories are cloned or refreshed on demand. Results include repository, revision, path, line, snippet, and a [owner/repo@revision:path:line] citation. Per-repository failures are reported as warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | maximum matches, from 1 to 100 |
| query | string | yes | literal text by default, or a regular expression when regex is true |
| regex | boolean | – | interpret query as a regular expression; false uses literal search |
| repos | null|array | – | optional repository slugs (owner/repo); defaults to all configured repositories |
No output schema declared.
No examples provided.
project_repo_list ~34
List the configured repository slugs (owner/repo) that this server can search. Call once to see what is available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_repo_sync ~57
Force-refresh one repository (or all configured repositories) in the server cache. This only updates the read-only cache; it never modifies the remote repository.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | optional repository slug to refresh; defaults to all configured repositories |
No output schema declared.
No examples provided.
project_symbol_search ~87
Search symbol definitions (Universal Ctags) by name fragment across one or more repositories. Repositories are cloned or refreshed on demand.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | maximum matches, from 1 to 100 |
| query | string | yes | symbol name or distinctive symbol fragment |
| repos | null|array | – | optional repository slugs (owner/repo); defaults to all configured repositories |
No output schema declared.
No examples provided.
How do I install the Project Brain MCP server?
Project Brain runs locally as a container image, launched with docker run --rm -i -e PROJECT_BRAIN_REPO_LIST -e PROJECT_BRAIN_STATE_DIR -e PB_GITHUB_TOKEN -e PB_FETCH_TTL ghcr.io/gentleelephant/project-brain:v2.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/gentleelephant/project-brain:v2.0.3
claude mcp add gentleelephant-project-brain -- docker run --rm -i -e PROJECT_BRAIN_REPO_LIST -e PROJECT_BRAIN_STATE_DIR -e PB_GITHUB_TOKEN -e PB_FETCH_TTL ghcr.io/gentleelephant/project-brain:v2.0.3
This image reads PROJECT_BRAIN_REPO_LIST, PROJECT_BRAIN_STATE_DIR, PB_GITHUB_TOKEN and PB_FETCH_TTL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Project Brain MCP server?
Project Brain is an MCP server listed in the public MCP registry as io.github.Gentleelephant/project-brain. Read-only source search and retrieval across configured GitHub repositories. This page covers its container image (ghcr.io/gentleelephant/project-brain:v2.0.3).
Is the Project Brain MCP server safe to use?
Project Brain scores 49 out of 100 on VerifyMCP. 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 Project Brain MCP server expose?
Project Brain exposes 6 tools: project_code_files, project_code_read, project_code_search, project_repo_list, project_repo_sync, project_symbol_search. Their descriptions and schemas cost roughly 554 tokens of context every time the server is loaded.
Is the Project Brain MCP server still maintained?
Project Brain is still listed as active in the MCP registry. We last reached this channel on 16 October 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 Project Brain MCP server under?
Project Brain declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.