Nelly the Elephant
NPM · NELLY-ELEPHANT-MCP · SCANNED SEP 20
Search and resume past Claude Code conversations. An elephant never forgets.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 173 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1550 tokens (~387/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the Nelly the Elephant MCP server?
Nelly the Elephant runs locally as an npm package, launched with npx -y nelly-elephant-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · nelly-elephant-mcp
claude mcp add spicyricecakes-nelly-elephant-mcp -- npx -y nelly-elephant-mcp
{
"mcpServers": {
"spicyricecakes-nelly-elephant-mcp": {
"command": "npx",
"args": [
"-y",
"nelly-elephant-mcp"
]
}
}
} {
"servers": {
"spicyricecakes-nelly-elephant-mcp": {
"command": "npx",
"args": [
"-y",
"nelly-elephant-mcp"
]
}
}
} codex mcp add spicyricecakes-nelly-elephant-mcp -- npx -y nelly-elephant-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"spicyricecakes-nelly-elephant-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"nelly-elephant-mcp"
],
"enabled": true
}
}
} openclaw mcp add spicyricecakes-nelly-elephant-mcp --command npx --arg -y --arg nelly-elephant-mcp
mcp_servers:
spicyricecakes-nelly-elephant-mcp:
command: "npx"
args: ["-y", "nelly-elephant-mcp"] {
"McpServers": {
"spicyricecakes-nelly-elephant-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"nelly-elephant-mcp"
]
}
}
} assistant mcp add spicyricecakes-nelly-elephant-mcp -t stdio -c npx -a -y nelly-elephant-mcp
{
"mcpServers": {
"spicyricecakes-nelly-elephant-mcp": {
"command": "npx",
"args": [
"-y",
"nelly-elephant-mcp"
]
}
}
} 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.
- 19 Sept 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 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.
- 13 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 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.
- 9 Sept 26 −2
- 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 20 Sept 2026 · Analysed npm/nelly-elephant-mcp@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
nelly_context ~88
Get expanded context from a specific session. Use this after nelly_search when the user wants to see more detail from a particular session before resuming it.
| Name | Type | Req | Description |
|---|---|---|---|
| context_lines | integer | – | Number of surrounding lines to include (default: 5) |
| query | string | yes | The search term to find context around |
| session_id | string | yes | The session ID to get context from |
No output schema declared.
No examples provided.
nelly_instructions ~39
Check Nelly's status — platform, sessions directory, and whether session data exists. Useful for diagnostics. Instructions are already loaded via MCP init.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nelly_recent ~64
List the most recent Claude Code sessions. Useful when the user doesn't remember specific keywords but knows it was recent.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of recent sessions to show (default: 10) |
| project | string | – | Filter to a specific project (partial match) |
No output schema declared.
No examples provided.
nelly_search ~118
Search past Claude Code conversations. Nelly searches through all session transcripts for matching keywords and returns sessions with snippets and resume commands. Use multiple searches with different terms for best results (spiral search pattern).
| Name | Type | Req | Description |
|---|---|---|---|
| days_back | integer | – | Only search sessions from the last N days |
| max_results | integer | – | Maximum number of sessions to return (default: 10) |
| project | string | – | Filter to a specific project directory (partial match) |
| query | string | yes | Search query — keywords or phrases to find in past conversations |
No output schema declared.
No examples provided.
What is the Nelly the Elephant MCP server?
Nelly the Elephant is an MCP server listed in the public MCP registry as io.github.SpicyRiceCakes/nelly-elephant-mcp. Search and resume past Claude Code conversations. An elephant never forgets. This page covers its npm package (nelly-elephant-mcp).
Is the Nelly the Elephant MCP server safe to use?
Nelly the Elephant scores 80 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. 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 Nelly the Elephant MCP server expose?
Nelly the Elephant exposes 4 tools: nelly_instructions, nelly_search, nelly_context, nelly_recent. Their descriptions and schemas cost roughly 309 tokens of context every time the server is loaded.
Is the Nelly the Elephant MCP server still maintained?
Nelly the Elephant 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 Nelly the Elephant MCP server under?
Nelly the Elephant declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.