SpikeMe
NPM · SPIKEME-MCP · SCANNED AUG 3
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 →
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 15 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · spikeme-mcp
claude mcp add isaacviannadev-spikeme -- npx -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": {
"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.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +34
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- 26 Jul 26 41
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
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.