toolpin MCP server
dev.toolpin/toolpintoolpin.devstreamable-httpv0.1.0Scanned
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
6 tools: 1 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the toolpin MCP server can do
The toolpin MCP server is published by toolpin.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: watch_server), but cannot delete data. 5 tools only read.
1 tool reads private data (get_server).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 1Claude Code: ask
watch_serverStart monitoring an MCP server on the caller's Toolpin account, so they are emailed when it changes or stops answering.No findings
Why it is in this group
- The description's first verb is "start": a word for a change.
Description, as the server wrote it 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.
Only reads 5Show 5 read-only tools
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-d…Reads private dataNo findings
Why it is in this group
- The name "get_server" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "repository": it reads repositories.
Description, as the server wrote it 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.
get_server_changesChanges Toolpin recorded for one MCP server: tool definitions changing, and endpoints going down or coming back.No findings
Why it is in this group
- The name "get_server_changes" says "get": a word for reading.
Description, as the server wrote it 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.
get_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.No findings
Why it is in this group
- The name "get_server_tools" says "get": a word for reading.
Description, as the server wrote it 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.
get_spec_statusThe current MCP specification revision, which of its proposals Toolpin checks for, and how much of the catalog has migrated.No findings
Why it is in this group
- The name "get_spec_status" says "get": a word for reading.
Description, as the server wrote it 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.
search_serversFind MCP servers in the public registry by name or title.No findings
Why it is in this group
- The name "search_servers" says "search": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://toolpin.dev/mcp: tools/list returned 6 tools to an anonymous client, including watch_server (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http toolpin https://toolpin.dev/mcpclaude mcp add --transport http toolpin https://toolpin.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__toolpin__search_servers",
"mcp__toolpin__get_server",
"mcp__toolpin__get_server_tools",
"mcp__toolpin__get_server_changes",
"mcp__toolpin__get_spec_status"
],
"ask": [
"mcp__toolpin__watch_server"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as toolpin. Review it before you use it.
Capability tags behind 1 rule
- mcp__toolpin__get_server private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.toolpin/toolpin/verify?hash=e8cc9b0e90aa8cf8ff1397d8d42558831a761b8b5c9a2b4985923a83687d9f04" | jq -e '.changed == false'Pinned hash e8cc9b0e90aa, from Nov 11, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.toolpin/toolpin/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.toolpin/toolpin)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.
toolpin MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the toolpin MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the toolpin MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the toolpin MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the toolpin MCP server have?
- 6 tools: 1 write, 5 read. watch_server, search_servers, get_server, get_server_tools, get_server_changes and get_spec_status.
Does the toolpin MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the toolpin MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the toolpin MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.