Skip to content

Toolpin MCP server

Which MCP servers are Toolpin's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Toolpin

Whose server it is
  • Registry namedev.toolpin/toolpinverified in the MCP registry

The registry name sits under toolpin.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools6
  • Server calls itselftoolpin
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 75 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Check whether a public MCP server's tools have changed; Get alerted when a watched server goes unreachable or recovers.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "Check whether a public MCP server's tools have changed", the likely first call is get_server_changes.
  • For "Get alerted when a watched server goes unreachable or recovers", the likely first call is watch_server.
  • Parameters are untyped or undescribed in 5 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer139 ms
  • Space in an agent's context≈ 679 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsC · 69 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 5 of 6
  • Not saying whether it only reads or can destroy: 6 of 6

What an agent can do with it

  • can do · Check whether a public MCP server's tools have changed
  • can do · Get alerted when a watched server goes unreachable or recovers
  • not sure · Verify an MCP server's tool claims before installing it

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-26
  • search_servers

    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.

  • get_server

    Everything 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…

  • get_server_tools

    The 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…

  • get_server_changes

    Changes 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…

  • get_spec_status

    The 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.

  • watch_server

    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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http toolpin https://toolpin.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://toolpin.dev/mcp as a custom connector in the settings.

OpenAPI spec

13 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.