Is the Toolpin MCP server down?

mcp-registry/dev.toolpin/toolpin · v0.1.0

Also listed as github/toolpin/mcp-server

healthy
Last checked 2026-10-20 19:04 UTC · handshake 126ms

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.

uptime (30d checks)
100%
checks observed
3,969
outages (90d)
0
tools
6

Check whether an MCP server answers, what its tools claim, and whether that claim has changed.

Install Toolpin MCP server

Add to Cursor Add to VS Code

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.

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 3 warning(s) across 6 tool(s); ~754 tokens of tool definitions.
Scores higher than 5% of 15,413 MCP servers Glimind has audited.
Its tool list costs an agent ~754 tokens per session — lighter than 85% of servers.
70 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions32
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

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 →

Tools: get_server, get_server_changes, get_server_tools, get_spec_status, search_servers and 1 more

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 →

Tools: get_server, get_server_changes, get_server_tools, search_servers, watch_server

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 →

Auto-fix: 5 corrected tool definitions

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

get_server 1 change
{
  "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
  }
}
get_server_changes 1 change
{
  "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
  }
}
get_server_tools 1 change
{
  "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 alerted

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.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.toolpin%2Ftoolpin.svg)](https://glimind.com/server/mcp-registry%2Fdev.toolpin%2Ftoolpin?ref=badge)
HTML
<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>
reStructuredText
.. 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

Tool-definition log

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.

Tools (6)

Compare: most reliable data servers · most reliable knowledge servers · most reliable search servers · most reliable devops servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Toolpin MCP server down right now?

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.

How many tools does Toolpin MCP server provide?

Toolpin MCP server advertises 6 tools, including get_server, get_server_changes, get_server_tools, get_spec_status, search_servers.

How do I install Toolpin MCP server?

Point your MCP client at this streamable-http endpoint: https://toolpin.dev/mcp

Is the Toolpin MCP server safe to connect to an AI agent?

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.

Operator of Toolpin MCP server?

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.

Feedback
Help us improve