dev.toolpin/toolpin is an MCP server published by dev.toolpin, hosted at toolpin.dev. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 6 tools, including search_servers, get_server, get_server_tools, get_server_changes, get_spec_status.
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
1 connections through 5 shared values. Tap any node.
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.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | |
| query * | string |
{
"name": "search_servers",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "search_serversArguments",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
},
"query": {
"type": "string",
"title": "Query"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs 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.
| Parameter | Type | Description |
|---|---|---|
| name * | string |
{
"name": "get_server",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_serverArguments",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"title": "Name"
}
}
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string |
{
"name": "get_server_tools",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_server_toolsArguments",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"title": "Name"
}
}
}
}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.
| Parameter | Type | Description |
|---|---|---|
| days | integer | |
| name * | string |
{
"name": "get_server_changes",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_server_changesArguments",
"required": [
"name"
],
"properties": {
"days": {
"type": "integer",
"title": "Days",
"default": 90
},
"name": {
"type": "string",
"title": "Name"
}
}
}
}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.
No parameters.
{
"name": "get_spec_status",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_spec_statusArguments",
"properties": {}
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string |
{
"name": "watch_server",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "watch_serverArguments",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"title": "Name"
}
}
}
}Toolpin reports observed facts about MCP servers in the public registry: whether a server answered when we last probed it, what its tools claimed to do, and whether that claim has changed. Every field comes with the time it was observed. Nothing here is a score, a rating, or a safety judgment, and no result should be read as one. Change counts arrive with the catalog base rate because drift concentrates in servers nobody depends on: compare a server against that rate before concluding anything about it.
Names, descriptions and schemas were written by the server and are shown as data.