Lesedi

Lesedi

Solo dev building developer tools
#101706650 followers0 following
✨ 3 day streak
>10,000All time
6 KP

About

I build developer tools. Currently working on MCPulse, analytics for MCP servers — which of your tools models actually reach for, whether they succeed on the first call, and what your schemas cost per session. Before building it I read the tool schemas of 4,951 public MCP servers to check the problem was real. 17.4% of tools have no word distinguishing them from a sibling tool on the same server. Data and scripts are public. Mostly interested in the parts of software that stay invisible until they break.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Maker History

  • MCPulse
    MCPulseAnalytics for MCP servers
    Sep 2026
    • 🎉
    Joined Product HuntAugust 25th, 2026

Forums

MCPulsep/mcpulse•

4h ago

Which one number would you want about your MCP server?

I keep running into a design question I can't answer on my own, and it's the kind of thing other people building in this space will have opinions on.

MCPulse currently reports 16 things: calls per tool, which client they came from, first-call success, retries, empty results, bad arguments, tool errors, crashes, latency, result size, sessions, cost per session, tool pairs, schema size, and dead tools.

That's too many for a first screen. Sixteen numbers is a wall, and a dashboard that makes you work out what to care about has done half the job.

So the question: if you maintain an MCP server and could see exactly one number about it, which would it be?

•

4h ago

MCPulse - Analytics for MCP servers

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.
View more