dev.toolpinPublished by toolpin.devOfficial publisherv0.1.0Updated Oct 25, 2026
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
A remote MCP server that reports on other MCP servers: reachability, advertised tool definitions, hashes and recorded changes.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.toolpin%2Ftoolpin/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"toolpin": {
"type": "http",
"url": "https://toolpin.dev/mcp"
}
}
}An MCP server that answers questions about other MCP servers: whether one answered when we last probed it, what its tools claimed to do, and whether that claim has changed since.
Useful when an agent is choosing which server to depend on, and useful in the moment something breaks and you want to know whether the tools moved under you.
https://toolpin.dev/mcp Streamable HTTP, stateless, no sign-up.
Full parameters and response shapes: https://toolpin.dev/api, or the machine-readable schema at https://toolpin.dev/openapi.json.
No key needed to read. Add one as an Authorization: Bearer header to raise the
limit, and to use watch_server, which acts on your account.
The limit counts distinct servers, not requests. Asking about the same servers all day costs one against the limit each, however often you ask, so watching your own dependencies never runs out. Never put a key in a URL.
No score, no grade, no rating, no safety judgment. Tool descriptions and annotations are reproduced exactly as the server published them: they are claims by that server's author, not anything Toolpin verified. A tool whose annotations say it only reads may do anything at all.
What Toolpin can tell you is whether the claim changed, because it hashes the fields the MCP specification defines and compares them daily. That is the whole product.
Methodology: https://toolpin.dev/methodology
Documentation and the published registry manifest. The service itself is closed source. Tool-definition changes are recorded in CHANGELOG.md, which is the same thing Toolpin watches for on everyone else.
Questions: [email protected]
Source: README.md at commit 3f6eefc
Find MCP servers in the public registry by name or title. Returns the canonical name, description, and whether the server answered our last probe. Use this to turn a rough idea of a server into the exact name the other tools need.
limitqueryrequiredEverything Toolpin has observed about one MCP server: reachability of each remote endpoint and when each was last checked and last verified, repository activity, the current tool-definition hash, and how many changes it has recorded in the last 90 days. The reply includes the catalog-wide drift rate so that count can be read against a baseline.
namerequiredThe tool definitions one MCP server advertised when Toolpin last read them, each with a SHA-256 hash of the fields the MCP specification defines. Use this to see what a server's tools claim to do without connecting to it, or to compare a hash you pinned earlier.
namerequiredChanges Toolpin recorded for one MCP server: tool definitions changing, and endpoints going down or coming back. Each change says which tools moved and which of their fields differed, with the hash before and after. Includes the catalog-wide drift rate for comparison.
daysnamerequiredThe current MCP specification revision, which of its proposals Toolpin checks for, and how much of the catalog has migrated. Use this to find out what the current revision is and how unusual it is to still be on an older one.
Takes no parameters.
Start monitoring an MCP server on the caller's Toolpin account, so they are emailed when it changes or stops answering. Needs an API key. Says so plainly if the account is already at its plan limit rather than failing.
namerequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
{ "mcpServers": { "toolpin": { "url": "https://toolpin.dev/mcp" } }}