# Toolpin MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.toolpin%2Ftoolpin
Registry id: `mcp-registry/dev.toolpin/toolpin`
Status: live (checked 2026-10-27T02:15:40.623Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4941
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "toolpin-mcp-server": {
      "type": "http",
      "url": "https://toolpin.dev/mcp"
    }
  }
}
```

Claude Code:

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

## Tools (6)

- `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
- `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
- `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 se
- `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 curre
- `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 t
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.