# SpikeMe (npm · spikeme-mcp)

Analyze your repo's stack and generate grounded, time-boxed spike decision docs.

- Trust score: 64/100 (medium)
- Change this week: −11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `spikeme-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/isaacviannadev-spikeme/spikeme-mcp.md), [page](https://verifymcp.io/servers/isaacviannadev-spikeme/spikeme-mcp)

## Channel facts

- Registry: `npm`
- Package: `spikeme-mcp`
- Version: `0.5.5`
- 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-08-03.

- **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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 376 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

### Claude

```bash
claude mcp add isaacviannadev-spikeme -- npx -y spikeme-mcp
```

### Codex

```bash
codex mcp add isaacviannadev-spikeme -- npx -y spikeme-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add isaacviannadev-spikeme --command npx --arg -y --arg spikeme-mcp
```

### Hermes

```yaml
mcp_servers:
  isaacviannadev-spikeme:
    command: "npx"
    args: ["-y", "spikeme-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "isaacviannadev-spikeme": {
      "command": "npx",
      "args": [
        "-y",
        "spikeme-mcp"
      ]
    }
  }
}
```

## 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-08-02 (score 64, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-01 (score 49, −8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 57, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 75, +34)

- [functional improvement] 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

### 2026-07-26 (score 41)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `analyze_stack` (~67 tokens)

Analyze stack

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.

Input parameters:

- `path` (string): Repo directory to analyze (default: current working directory)

### `generate_spike` (~156 tokens)

Generate spike

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.

Input parameters:

- `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, required): The technical decision to spike, e.g. "state management library" or "asyncpg vs psycopg".

### `generate_implementation` (~153 tokens)

Generate implementation guide

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.

Input parameters:

- `language` (string): Guide language (default: en)
- `library` (string, required): 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.

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 49
- 2026-07-31: 57
- 2026-07-29: 75
- 2026-07-28: 75
- 2026-07-27: 75
- 2026-07-26: 41

## Links

- npm package: https://www.npmjs.com/package/spikeme-mcp
- Socket report: https://socket.dev/npm/package/spikeme-mcp
- Website: https://spikeme.io/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/isaacviannadev-spikeme/spikeme-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/isaacviannadev-spikeme/spikeme-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/isaacviannadev-spikeme/spikeme-mcp