mcpField
T
toolpin

toolpin

Remote
toolpin.devDeveloper Tools0Updated 1w ago

About toolpin

toolpin is an MCP server for looking up and monitoring other MCP servers, useful when selecting dependencies or investigating failures. It tracks changes to tool definitions using hashes of specification-defined fields, but does not provide ratings or safety judgments.

Key features

  1. 01Search MCP servers by name or title
  2. 02Check endpoint reachability and check times
  3. 03Retrieve observed tool definitions
  4. 04Review endpoint and tool change history
  5. 05Monitor servers and receive change emails
  6. 06Check MCP specification and migration status

Use cases

  1. 01Check an MCP server before relying on it
  2. 02Verify whether tool definitions have changed
  3. 03Investigate remote endpoint outages or recovery
  4. 04Subscribe to change alerts for dependencies

MCP support

toolpin is a stateless MCP server available over Streamable HTTP. It exposes tools for searching other MCP servers and querying their status, tool definitions, and recorded changes; monitoring requires account authorization.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://toolpin.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

6
ParameterTypeRequiredDescription
limitintegerNo
querystringYes

Details

From the project README

Toolpin MCP server

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.

{
  "mcpServers": {
    "toolpin": {
      "url": "https://toolpin.dev/mcp"
    }
  }
}

Tools

ToolWhat it answers
search_serversFind MCP servers in the public registry by name or title.
get_serverEverything 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.
get_server_toolsThe tool definitions one MCP server advertised when Toolpin last read them, each with a SHA-256 hash of the fields the MCP specification defines.
get_server_changesChanges Toolpin recorded for one MCP server: tool definitions changing, and endpoints going down or coming back.
get_spec_statusThe current MCP specification revision, which of its proposals Toolpin checks for, and how much of the catalog has migrated.
watch_serverStart monitoring an MCP server on the caller's Toolpin account, so they are emailed when it changes or stops answering.

Full parameters and response shapes: https://toolpin.dev/api, or the machine-readable schema at https://toolpin.dev/openapi.json.

Limits

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.

CallerDistinct servers per day
Anonymous25
Signed in, free200
Any paid planUnmetered

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.

What it will not tell you

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

This repository

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]

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.