# Spiderbrain (npm · spiderbrain)

Deterministic context layer for your codebase: change impact, blast radius, answers with receipts.

- Trust score: 93/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.spiderbrain.ai`: 36/100, [markdown](https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/mcp.md), [page](https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/mcp)
- npm · `spiderbrain`: 93/100 (this document), [markdown](https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/spiderbrain.md), [page](https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/spiderbrain)

## Channel facts

- Registry: `npm`
- Package: `spiderbrain`
- Version: `0.2.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 2 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to aabhisrv/Spiderbrain.ai-Coremind).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 28 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 241 tokens (~40/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 29% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add ai-spiderbrain-spiderbrain -- npx -y spiderbrain
```

### Cursor

```json
{
  "mcpServers": {
    "ai-spiderbrain-spiderbrain": {
      "command": "npx",
      "args": [
        "-y",
        "spiderbrain"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-spiderbrain-spiderbrain": {
      "command": "npx",
      "args": [
        "-y",
        "spiderbrain"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ai-spiderbrain-spiderbrain -- npx -y spiderbrain
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-spiderbrain-spiderbrain": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "spiderbrain"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-spiderbrain-spiderbrain --command npx --arg -y --arg spiderbrain
```

### Hermes

```yaml
mcp_servers:
  ai-spiderbrain-spiderbrain:
    command: "npx"
    args: ["-y", "spiderbrain"]
```

### Netclaw

```json
{
  "McpServers": {
    "ai-spiderbrain-spiderbrain": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "spiderbrain"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-spiderbrain-spiderbrain -t stdio -c npx -a -y spiderbrain
```

### Other

```json
{
  "mcpServers": {
    "ai-spiderbrain-spiderbrain": {
      "command": "npx",
      "args": [
        "-y",
        "spiderbrain"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 93, +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.

### 2026-09-18 (score 92, +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.

### 2026-09-16 (score 91, +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.

### 2026-09-14 (score 90, +1)

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

### 2026-09-12 (score 89, +1)

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

### 2026-09-10 (score 88, +1)

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

### 2026-09-08 (score 87, +1)

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

### 2026-09-05 (score 86, +1)

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

## MCP tools (6)

### `sb_blast` (~45 tokens)

What a change to a file reaches (its transitive dependents / blast radius), computed deterministically from the committed graph.

Input parameters:

- `path` (string, required): repo-relative file path

### `sb_impact` (~56 tokens)

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.

Input parameters:

- `paths` (array, required): repo-relative paths of the changed files

### `sb_path` (~43 tokens)

The shortest dependency path between two files: how does one reach the other (import chain or dependent chain).

Input parameters:

- `from` (string, required)
- `to` (string, required)

### `sb_keystones` (~30 tokens)

The load-bearing files, ranked by how many files they reach.

Input parameters:

- `n` (number)

### `sb_map` (~31 tokens)

What a file is, what it depends on, and what depends on it.

Input parameters:

- `path` (string, required)

### `sb_ask` (~36 tokens)

Ask about the repo. Structure is answered offline; the why-layer needs a SpiderBrain API key.

Input parameters:

- `question` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/spiderbrain#diagnostics

## Score history

- 2026-09-20: 93
- 2026-09-19: 92
- 2026-09-18: 92
- 2026-09-17: 91
- 2026-09-16: 91
- 2026-09-15: 90
- 2026-09-14: 90
- 2026-09-13: 89
- 2026-09-12: 89
- 2026-09-11: 88
- 2026-09-10: 88
- 2026-09-09: 87
- 2026-09-08: 87
- 2026-09-07: 86
- 2026-09-06: 86
- 2026-09-05: 86
- 2026-09-04: 85
- 2026-09-03: 85
- 2026-09-02: 84
- 2026-09-01: 84
- 2026-08-31: 83
- 2026-08-30: 83
- 2026-08-29: 79
- 2026-08-28: 79
- 2026-08-27: 79
- 2026-08-26: 79
- 2026-08-25: 77
- 2026-08-24: 77
- 2026-08-23: 77
- 2026-08-22: 77

## Common questions

### 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 20 September 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 20 September 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.

## Links

- npm package: https://www.npmjs.com/package/spiderbrain
- Socket report: https://socket.dev/npm/package/spiderbrain
- Repository: https://github.com/aabhisrv/Spiderbrain.ai-Coremind
- Website: https://spiderbrain.ai/api/
- Changelog RSS feed: https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/spiderbrain.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/spiderbrain.json
- HTML version of this page: https://verifymcp.io/servers/ai-spiderbrain-spiderbrain/spiderbrain