Spiderbrain
NPM · SPIDERBRAIN · 2 COMPONENTS
Deterministic context layer for your codebase: change impact, blast radius, answers with receipts.
Available components
Last scanned (20 minutes ago)
Scores higher than 96% of npm 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 2 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aabhisrv/Spiderbrain.ai-Coremind). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 74 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 241 tokens (~40/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% of tool parameters carry a description.Partial
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 6 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
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.
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 −1
- Stability: pass → 0.93 functional
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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
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 5 Nov 2026 · Analysed npm/spiderbrain@0.2.3
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | aabhisrv/Spiderbrain.ai-Coremind |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aabhisrv/Spiderbrain.ai-Coremind/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2567709781 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5f741142c2c8887448d400d3b0222da1854d4912c1d1df84153e31bbf5eaee5093c4c0d0702585da83f2f8d50c16377a36ff96a7852cd35ddb5714dc9 |
Background: How many MCP packages publish verified provenance →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
sb_ask ~36
Ask about the repo. Structure is answered offline; the why-layer needs a SpiderBrain API key.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
No output schema declared.
No examples provided.
sb_blast ~45
What a change to a file reaches (its transitive dependents / blast radius), computed deterministically from the committed graph.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | repo-relative file path |
No output schema declared.
No examples provided.
sb_impact ~56
What a CHANGE SET reaches: the union blast of several changed files, plus which changed files are keystones. Use before/while editing to know the consequences.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | repo-relative paths of the changed files |
No output schema declared.
No examples provided.
sb_keystones ~30
The load-bearing files, ranked by how many files they reach.
| Name | Type | Req | Description |
|---|---|---|---|
| n | number | – | – |
No output schema declared.
No examples provided.
sb_map ~31
What a file is, what it depends on, and what depends on it.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
sb_path ~43
The shortest dependency path between two files: how does one reach the other (import chain or dependent chain).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Spiderbrain MCP server?
Spiderbrain runs locally as an npm package, launched with npx -y spiderbrain. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · spiderbrain
claude mcp add ai-spiderbrain-spiderbrain -- npx -y spiderbrain
What is the Spiderbrain MCP server?
Spiderbrain is an MCP server listed in the public MCP registry as ai.spiderbrain/spiderbrain. Deterministic context layer for your codebase: change impact, blast radius, answers with receipts. This page covers its npm package (spiderbrain).
Is the Spiderbrain MCP server safe to use?
Spiderbrain scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Spiderbrain MCP server expose?
Spiderbrain exposes 6 tools: sb_blast, sb_impact, sb_path, sb_keystones, sb_map, sb_ask. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Is the Spiderbrain MCP server still maintained?
Spiderbrain is still listed as active in the MCP registry. We last reached this channel on 5 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 Spiderbrain MCP server under?
Spiderbrain declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.