Skip to content

dev.toolpin/toolpin

by toolpin.dev · remote · no sign-in to list tools · v0.1.0 · published by dev.toolpin

Check whether an MCP server answers, what its tools claim, and whether that claim has changed.

Changes · 1
CompareRegistry entry

6 tools: 1 change things and 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 1Claude Code: ask
  • watch_serverStart monitoring an MCP server on the caller's Toolpin account, so they are emailed when it changes or stops answering.No findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    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.
Only reads 5Claude Code: allow
  • 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-d…No findings

    Why it is in this group

    • The name "get_server" says "get": a word for reading.
    Description, as the server wrote it
    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 the last 90 days. The reply includes the catalog-wide drift rate so that count can be read against a baseline.
  • get_server_changesChanges Toolpin recorded for one MCP server: tool definitions changing, and endpoints going down or coming back.No findings

    Why it is in this group

    • The name "get_server_changes" says "get": a word for reading.
    Description, as the server wrote it
    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 catalog-wide drift rate for comparison.
  • 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.No findings

    Why it is in this group

    • The name "get_server_tools" says "get": a word for reading.
    Description, as the server wrote it
    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 hash you pinned earlier.
  • get_spec_statusThe current MCP specification revision, which of its proposals Toolpin checks for, and how much of the catalog has migrated.No findings

    Why it is in this group

    • The name "get_spec_status" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • search_serversFind MCP servers in the public registry by name or title.No findings

    Why it is in this group

    • The name "search_servers" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__toolpin__search_servers",
      "mcp__toolpin__get_server",
      "mcp__toolpin__get_server_tools",
      "mcp__toolpin__get_server_changes",
      "mcp__toolpin__get_spec_status"
    ],
    "ask": [
      "mcp__toolpin__watch_server"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as toolpin. Review it before you use it.