mcp-registry/dev.toolpin/toolpin · v0.1.0
Also listed as github/toolpin/mcp-server
As of 2026-10-20 19:04 UTC, the Toolpin MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
Claude Code
claude mcp add --transport http toolpin-mcp-server https://toolpin.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"toolpin-mcp-server": {
"type": "http",
"url": "https://toolpin.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
7 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~1,852 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.toolpin%2Ftoolpin/fixes
{
"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"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"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"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"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"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.toolpin/toolpin"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.toolpin/toolpin"}) over MCP.
get_server ~145 tokensget_server_changes ~143 tokenssearch_servers ~132 tokensget_server_tools ~125 tokenswatch_server ~111 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.toolpin%2Ftoolpin?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.toolpin%2Ftoolpin?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.toolpin%2Ftoolpin.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.toolpin%2Ftoolpin.svg :target: https://glimind.com/server/mcp-registry%2Fdev.toolpin%2Ftoolpin?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8f6f056f68a2e8b1…, first seen 2026-10-17, included at leaf 5346 of 34,586. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable search servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 19:04 UTC, the Toolpin MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Toolpin MCP server advertises 6 tools, including get_server, get_server_changes, get_server_tools, get_spec_status, search_servers.
Point your MCP client at this streamable-http endpoint: https://toolpin.dev/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.