MCP Pulse

CLI reliability monitor for TypeScript/Node MCP servers. Zero code changes required.

Your MCP server is either production-ready or it isn't. MCP Pulse tells you which.

Install

npm install -g @mcppulse/cli

Node 18+ · macOS, Linux, Windows · zero config

Usage

# Wrap any MCP server
mcp-pulse -- npx @modelcontextprotocol/server-filesystem /tmp
mcp-pulse -- node ./my-server.js

# Score your server
mcp-pulse score

# Generate a report
mcp-pulse report

# Auto-wrap Claude Desktop / Cursor configs
mcp-pulse init

MCP Pulse acts as a transparent stdio proxy. Bytes are forwarded byte-for-byte — your clients never know it's there.

What it measures

| Component | Weight | What it detects | |---|---|---| | Success Rate | 35 | Failed tool calls, error responses | | Latency Stability | 25 | p95 vs p50 spread — jitter under load | | Schema Consistency | 20 | Response shape drift across calls | | Error Resilience | 10 | Graceful handling of bad inputs | | Auth Posture | 10 | No auth → API key → OAuth 2.1 | | Spec v2 Compat | +5 | Ready for July 28, 2026 cutover |

Scores are 0–100. Grades: Production Ready (90+) · Stable (70–89) · Needs Improvement (50–69) · Unreliable (<50).

Full methodology: github.com/mcp-pulse/reliability-standard

Benchmark — June 2026

Scores from real traffic. Minimum 47 tool calls per server.

| Server | Score | Grade | Calls | |---|---|---|---| | @modelcontextprotocol/server-filesystem | 70/100 | Stable | 47 | | @modelcontextprotocol/server-memory | 70/100 | Stable | 47 | | @modelcontextprotocol/server-sequential-thinking | 70/100 | Stable | 47 |

Live badge data: https://badge.mcp-pulse.com/{server}.svg

Add a badge to your server

[![MCP Pulse](https://badge.mcp-pulse.com/your-server-name.svg)](https://mcp-pulse.com)

To get your server scored:

1. npm install -g @mcppulse/cli
2. mcp-pulse -- node ./your-server.js
3. Run 50+ tool calls through Claude Desktop or Cursor
4. mcp-pulse score

Spec v2 — July 28, 2026 cutover

The MCP spec v2 hard cutover breaks all v1.x servers:

• Sessions eliminated → stateless
• _meta required on every request (not just initialize)
• Error code -32002 → -32602
• New required headers

MCP Pulse detects v2 incompatibilities in real-time and flags them in the terminal report.

Data privacy

MCP Pulse captures shapes only — JSON key names, never values. No PII is stored.

environment_id is sha256(machine_id + project_path) — no email, no name.

Tiers

| Tier | Price | Features | |---|---|---| | Free | $0 | Local, 7-day history, terminal report | | Starter | $29/mo | 30-day history, PDF report, fix suggestions, email alerts | | Team | $99/mo | Cross-user benchmarks, dashboard, Slack alerts, spec v2 view | | Security | $299/mo | Real-time dangerous method alerts, audit export, SSRF detection | | Enterprise | $599/mo | Self-hosted, RBAC, compliance export, SLA |

Links

• Website: mcp-pulse.com
• Scoring standard: github.com/mcp-pulse/reliability-standard
• npm: @mcppulse/cli