A public record of claude-flow's tool definitions over time

[GautamTalksDev]

Hi,

I've been building a public log of MCP tool definitions, because clients ask a user to approve a server once and then never re-check. If a description changes in a later release, nothing tells that user.

Here's the page for claude-flow: https://mcp-pin.gautamkhosla.com/servers/2cc8ab5b251009f8.html

333 tools and 120,899 characters of description, which is the largest surface I've fingerprinted so far. I also noticed it ships under two package names, claude-flow and ruflo, with identical tool sets, so I've tracked both separately: https://mcp-pin.gautamkhosla.com/servers/64e9436dfbd00fb5.html. If those are meant to stay in sync, a divergence between them would show up here.

That much text is doing real work steering the model, and it's the case this is built for: a user approved those descriptions at some version and their client has not re-read them since. Everything is fingerprinted now, so any future change shows up as a dated diff rather than being invisible.

If it's useful, there's a badge:

No ask beyond that. If you'd rather not be crawled, say so and it stops, no explanation needed: https://mcp-pin.gautamkhosla.com/about.html

And if this is useless to you, telling me why would be the most helpful reply I could get.

Gautam

[GautamTalksDev]

Follow-up: here's a 35-second walkthrough of what this looks like when it fires, including a real change it caught on day one.

https://youtu.be/uDFFiV10hLo