MCPulse

Description

Analytics for MCP servers. Publish a server and you can see nothing — not how many people use it, which tools get called, whether the model understands your tool descriptions, or what your server costs the people using it. MCPulse answers that: calls, first-call success, retries, bad arguments, tool errors, crashes, empty results, latency and token cost, broken down per tool and per client. Install the [npm package](https://www.npmjs.com/package/@mcpulse/sdk) inside your own server and wrap it in two lines — no proxy, no DNS change, and your server keeps working if MCPulse is down

Community Metrics

Categories

• mcp

Tags

• mcp
• smithery

Capabilities

• Remote MCP server

Information