Categories › AI & Agents › Models, LLM APIs, routing, serving, training & GPUs
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
Remote server: your requests and data go to toolpin.dev. Claude Code: claude mcp add --transport http toolpin https://toolpin.dev/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 get_server — Everything Toolpin has observed about one MCP server: reachability of each remote endpoint and when each was last checked and last verified,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 defget_server_changes — Changes Toolpin recorded for one MCP server: tool definitions changing, and endpoints going down or coming back. Each change says which toolget_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 finwatch_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. SaNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.