SpikeMe
NPM · SPIKEME-MCP · SCANNED SEP 24
Analyze your repo's stack and generate grounded, time-boxed spike decision docs.
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 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 (MIT).Pass
- Actively maintained (last published 45 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
- Tool/resource definitions use about 376 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 SpikeMe MCP server?
SpikeMe runs locally as an npm package, launched with npx -y spikeme-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 · spikeme-mcp
claude mcp add isaacviannadev-spikeme -- npx -y spikeme-mcp
{
"mcpServers": {
"isaacviannadev-spikeme": {
"command": "npx",
"args": [
"-y",
"spikeme-mcp"
]
}
}
} {
"servers": {
"isaacviannadev-spikeme": {
"command": "npx",
"args": [
"-y",
"spikeme-mcp"
]
}
}
} codex mcp add isaacviannadev-spikeme -- npx -y spikeme-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"isaacviannadev-spikeme": {
"type": "local",
"command": [
"npx",
"-y",
"spikeme-mcp"
],
"enabled": true
}
}
} openclaw mcp add isaacviannadev-spikeme --command npx --arg -y --arg spikeme-mcp
mcp_servers:
isaacviannadev-spikeme:
command: "npx"
args: ["-y", "spikeme-mcp"] {
"McpServers": {
"isaacviannadev-spikeme": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"spikeme-mcp"
]
}
}
} assistant mcp add isaacviannadev-spikeme -t stdio -c npx -a -y spikeme-mcp
{
"mcpServers": {
"isaacviannadev-spikeme": {
"command": "npx",
"args": [
"-y",
"spikeme-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.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 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.
- 18 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 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
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 24 Sept 2026 · Analysed npm/spikeme-mcp@0.5.6
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
analyze_stack Analyze stack ~67
Analyze the dependency manifest(s) in a repo (package.json, pyproject.toml, requirements.txt, go.mod). Returns the stack, categories, and gaps that make good spike topics. Local and free.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Repo directory to analyze (default: current working directory) |
No output schema declared.
No examples provided.
generate_implementation Generate implementation guide ~153
Generate a concrete, actionable implementation guide for adopting a chosen library in this repo's real stack: exact version-pinned install commands, a minimal working example, integration steps, and a PoC checklist. SpikeMe writes the plan; it does NOT run anything — the calling agent executes under the user's confirmation. Requires `spikeme login` and an active plan.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Guide language (default: en) |
| library | string | yes | The chosen library/tool to implement, e.g. "zustand" or "asyncpg". |
| path | string | – | Repo directory (default: current working directory) |
| topic | string | – | Optional context, e.g. the decision this came from. |
No output schema declared.
No examples provided.
generate_spike Generate spike ~156
Generate a full spike decision document for a technical choice, grounded in the repo's real stack and live registry facts (versions, downloads, licenses). Requires the user to have run `spikeme login` in a terminal and to have an active plan.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | quick = shorter/cheaper; full = detailed (default) |
| language | string | – | Document language (default: en) |
| options | integer | – | How many options to compare (2-4, default 3) |
| path | string | – | Repo directory (default: current working directory) |
| topic | string | yes | The technical decision to spike, e.g. "state management library" or "asyncpg vs psycopg". |
No output schema declared.
No examples provided.
What is the SpikeMe MCP server?
SpikeMe is an MCP server listed in the public MCP registry as io.github.isaacviannadev/spikeme. Analyze your repo's stack and generate grounded, time-boxed spike decision docs. This page covers its npm package (spikeme-mcp).
Is the SpikeMe MCP server safe to use?
SpikeMe scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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 SpikeMe MCP server expose?
SpikeMe exposes 3 tools: analyze_stack, generate_spike, generate_implementation. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.
Is the SpikeMe MCP server still maintained?
SpikeMe is still listed as active in the MCP registry. We last reached this channel on 24 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 SpikeMe MCP server under?
SpikeMe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.