Developer Tools
toolpin.dev
Provides tools to search, inspect, and monitor public MCP servers, including their tool definitions, changes, endpoint status, and specification compliance.
ENDPOINT 1
https://toolpin.dev/mcp
MCP server metadata
- Name
- toolpin
- Version
- 0.1.0
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.
Known tools 6
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-definition hash, and how many changes it has recorded in the last 90 days.
Inferred read-onlyget_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.
Inferred read-onlyget_server_changesChanges Toolpin recorded for one MCP server: tool definitions changing, and endpoints going down or coming back.
Inferred read-onlyget_spec_statusThe current MCP specification revision, which of its proposals Toolpin checks for, and how much of the catalog has migrated.
Inferred read-onlywatch_serverStart monitoring an MCP server on the caller's Toolpin account, so they are emailed when it changes or stops answering.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.toolpin]
url = "https://toolpin.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"toolpin": {
"type": "http",
"url": "https://toolpin.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: toolpin
Remote MCP URL: https://toolpin.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"toolpin": {
"url": "https://toolpin.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"toolpin": {
"type": "http",
"url": "https://toolpin.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "toolpin",
"transport": "streamable-http",
"url": "https://toolpin.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.