A public record of codebase-memory-mcp'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 codebase-memory-mcp: https://mcp-pin.gautamkhosla.com/servers/9294479e6e70612f.html

query_graph at 1,803 characters and search_graph at 1,474 are two tools that sound close from the outside, so the descriptions are what tell the model which one to reach for. That makes them behavioural rather than documentary: change the text and you change the routing, without touching a line of code the user can see.

Add index_repository, which reads a whole codebase, and the case for a record gets fairly clear. All 15 tools are fingerprinted now, so any future change shows up as a dated diff.

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