MCPulse
Analytics for MCP servers
4 followers
Analytics for MCP servers
4 followers
Find out which of your tools agents get wrong. MCPulse shows you which tools AI agents retry, which come back empty, and which they never call at all. Two lines inside your own server. It never sees your arguments or your results.
Interactive
Free
Launch Team / Built With
Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free
Promoted
Hi Product Hunt
I built MCPulse because I published an MCP server and had no idea whether it worked. The directories tell you nothing — not how many people use it, not which tools get called, not whether the model can even understand your tool descriptions.
The thing that surprised me most is on the second image. One tool, search_orders, succeeds on the first try 76% of the time for Claude Desktop and 21% of the time for Cursor. Server-wide it averages out to a flat 62%, which tells you nothing to fix. The description is ambiguous, not the handler — and you cannot see that without splitting every metric by client, which is why every metrics table here is keyed by the client as well as the
tool.
Two things people ask straight away:
It is not a proxy. It is a package inside your own server, so your URL never changes and OAuth keeps working. If MCPulse is down, your server keeps running.
It never sees your data. Sizes and hashes only — there is no column for arguments or results, so it is not a policy I can quietly change later.
Ten languages, one for every official MCP SDK. Free forever and there is a live demo with no signup: app.getmcpulse.com/m/demo
Would love to know what you would want measured that isn't here yet