MCP.Market

Spikes MCP server

by bierlingm·io.github.bierlingm/spikes·v0.4.1·1 stars

UI feedback for AI-assisted building. Click elements, rate them, agents triage via MCP.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

1 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed Spikes yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Spikes tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Spikes compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
35
more than 25% of 12,191 servers with a package

Install Spikes in Claude Code, Cursor or VS Code

Runs npx -y spikes-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add spikes -- npx -y spikes-mcp
Add to Cursor

What the publisher says

From the Spikes repository's README, as published. We do not edit it. Read it on GitHub

/ Spikes

The feedback loop for AI-assisted building

AI can build a prototype in an hour. Turning feedback into action is still the slow part.

Quick Start · CLI Reference · Widget Docs · Hosted Dashboard · Self-Hosting

What Is This?

Spikes is a feedback tool for AI-assisted development. It lets reviewers leave targeted feedback directly on web pages — no screenshots, no "that button over there", no lost context.

Click any element. Rate it. Comment. Spikes captures the exact CSS selector, bounding box, and page context. Your AI agent gets structured JSON it can act on immediately.

No accounts required. No build step. Works on file://, localhost, anywhere.

Quick Start

1. Install the CLI

curl -fsSL https://spikes.sh/install.sh | sh
# Or: cargo install spikes

2. Initialize your project

spikes init                     # Defaults to hosted spikes.sh
# spikes init --self-host       # Opt out — scaffold a self-hosted config instead

spikes init creates .spikes/config.toml with a [remote] section pointing at https://spikes.sh by default. Pass --self-host (or answer s at the prompt) to skip the hosted defaults.

3. Add the widget to your HTML

spikes inject ./mockups/        # Injects widget script tag (uses configured endpoint)
spikes serve                    # http://localhost:3847

4. Collect and use feedback

spikes list                     # See all feedback
spikes list --json              # Feed to your agent
spikes list --rating no         # Find problems
spikes hotspots                 # Elements with most feedback
spikes resolve <id>             # Mark items done

CLI Commands

All commands support --json for scripting. See full CLI reference.

Viewing spikes for a hosted project:

The hosted dashboard at * lists every project you own and lets you drill into individual spikes (filter by page, rating, resolved, toggle resolved inline). Sign in directly in your browser: click Sign in**, open the verification page, and confirm via the magic link sent to your email — no CLI required.

You can also hit the JSON API directly with your bearer token ($SPIKES_TOKEN from spikes login):

# GET /me/projects
# List all projects you own (with spike_count + last_activity)
curl -H "Authorization: Bearer $SPIKES_TOKEN" \
  https://spikes.sh/me/projects

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Spikes: common questions

Is Spikes MCP server safe?
Mostly: it is graded B (83/100). Read the Spikes safety report
How do I install Spikes?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Spikes need an API key?
Yes. The registry entry asks for SPIKES_TOKEN.
Is Spikes maintained?
The last commit was 45 days ago (2026-09-20). The latest release is v0.4.1.
How does Spikes compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 35 (more than 25% of 12,191 servers with a package). Full comparison.