toolpin
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"toolpin": {
"url": "https://toolpin.dev/mcp"
}
}
}Remote endpoints
https://toolpin.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (6)
🟢search_servers(query, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"query": {
"title": "Query",
"type": "string"
},
"limit": {
"default": 10,
"title": "Limit",
"type": "integer"
}
},
"required": [
"query"
],
"title": "search_serversArguments"
}🟢get_server(name)
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.
Input Schema
{
"type": "object",
"properties": {
"name": {
"title": "Name",
"type": "string"
}
},
"required": [
"name"
],
"title": "get_serverArguments"
}🟢get_server_tools(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.
Input Schema
{
"type": "object",
"properties": {
"name": {
"title": "Name",
"type": "string"
}
},
"required": [
"name"
],
"title": "get_server_toolsArguments"
}🟡get_server_changes(name, days)
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.
Input Schema
{
"type": "object",
"properties": {
"name": {
"title": "Name",
"type": "string"
},
"days": {
"default": 90,
"title": "Days",
"type": "integer"
}
},
"required": [
"name"
],
"title": "get_server_changesArguments"
}🟢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.
Input Schema
{
"type": "object",
"properties": {},
"title": "get_spec_statusArguments"
}⚪watch_server(name)
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.
Input Schema
{
"type": "object",
"properties": {
"name": {
"title": "Name",
"type": "string"
}
},
"required": [
"name"
],
"title": "watch_serverArguments"
}Recommended Prompts
search_serversget_serversearch_serversget_serversearch_serversget_serverCommunity
Evidence