dev.toolpin/toolpin
REMOTE · TOOLPIN.DEV · SCANNED SEP 29
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 514 tokens (~85/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the dev.toolpin/toolpin MCP server?
dev.toolpin/toolpin is a hosted endpoint at https://toolpin.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · toolpin.dev
claude mcp add --transport http dev-toolpin-toolpin 'https://toolpin.dev/mcp'
{
"mcpServers": {
"dev-toolpin-toolpin": {
"url": "https://toolpin.dev/mcp"
}
}
} {
"servers": {
"dev-toolpin-toolpin": {
"type": "http",
"url": "https://toolpin.dev/mcp"
}
}
} [mcp_servers.dev-toolpin-toolpin] url = "https://toolpin.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-toolpin-toolpin": {
"type": "remote",
"url": "https://toolpin.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-toolpin-toolpin --url 'https://toolpin.dev/mcp' --transport streamable-http
mcp_servers:
dev-toolpin-toolpin:
url: "https://toolpin.dev/mcp" {
"McpServers": {
"dev-toolpin-toolpin": {
"Transport": "http",
"Url": "https://toolpin.dev/mcp"
}
}
} assistant mcp add dev-toolpin-toolpin -t streamable-http -u 'https://toolpin.dev/mcp'
{
"mcpServers": {
"dev-toolpin-toolpin": {
"type": "http",
"url": "https://toolpin.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://toolpin.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toolpin.dev | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e9846b167a63ad3e133a40e77a78ddbd |
| SANs: toolpin.dev, *.toolpin.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of toolpin.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| toolpin.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src data:; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://toolpin.dev/mcp | Verified | 200 | |
| http (plaintext) | http://toolpin.dev/mcp | HTTPS enforced | 301 | https://toolpin.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_server ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
get_server_changes ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
get_server_tools ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
get_spec_status ~56
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
watch_server ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
What is the dev.toolpin/toolpin MCP server?
dev.toolpin/toolpin is an MCP server listed in the public MCP registry as dev.toolpin/toolpin. Check whether an MCP server answers, what its tools claim, and whether that claim has changed. This page covers its hosted endpoint (https://toolpin.dev/mcp).
Is the dev.toolpin/toolpin MCP server safe to use?
dev.toolpin/toolpin scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dev.toolpin/toolpin MCP server expose?
dev.toolpin/toolpin exposes 6 tools: search_servers, get_server, get_server_tools, get_server_changes, get_spec_status, watch_server. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.
Does the dev.toolpin/toolpin MCP server require authentication?
No. We connected to dev.toolpin/toolpin without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.toolpin/toolpin MCP server still maintained?
dev.toolpin/toolpin is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.