Skip to content

A public record of currents-mcp's tool definitions over time #175

Description

@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 currents-mcp: https://mcp-pin.gautamkhosla.com/servers/3a4463759a3d1629.html

39 tools and 8,468 characters of description. Your naming is consistent enough that the descriptions are clearly doing the disambiguation work: currents-get-tests-performance and currents-get-spec-files-performance are close enough in name that what separates them, from the model's point of view, is the description text. A change to either one shifts which tool gets picked, and nothing surfaces that to a user who approved the server weeks ago.

All 39 are fingerprinted now, so any future change shows up as a dated diff. If it's useful, there's a badge:

mcp-pin

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions