mcp-pin
NPM · MCP-PIN
Check if an MCP server's tool definitions changed after approval, from a signed public log.
Available components
Last scanned (15 hours ago)
Scores higher than 82% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GautamTalksDev/mcp-pin). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 694 tokens (~173/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 17 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 16 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
- 14 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 11 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 7 Oct 26 35
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 22 Oct 2026 · Analysed npm/mcp-pin@0.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GautamTalksDev/mcp-pin |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GautamTalksDev/mcp-pin/.github/workflows/publish.yml@refs/tags/v0.2.3 |
| Rekor log index | 3110908684 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:48e2bd9ca2015f23c27cc6034ff73c87b30111f8ab97428dc5977bb5df06483c8a0b8ce4cb0e30e90fba6e683c4c838ee65030ffffd201364caf37f90 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mcp_pin_change_summary What kind of change is waiting ~172
Explain what kind of change mcp-pin blocked on one pinned server, without the changed text. Use it after mcp_pin_my_servers shows pending: true, to tell the user what they are about to review. Input: id, the 16-character server id from mcp_pin_my_servers. Returns one entry per changed tool, prompt or instruction block with label keys: new-tool, new-prompt, new-field, new-argument, instruction, secrets, link, hidden, hints, field-type, output-schema, field-removed, removed, wording. Approving is always the user's decision: never run "mcp-pin approve" for them.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Server id from mcp_pin_my_servers, for example "18d57558e558a5f4". |
No output schema declared.
No examples provided.
mcp_pin_how_to_protect How to protect MCP servers ~132
Give the exact steps to put mcp-pin in front of MCP servers in one AI app, so the user can copy them. Use it when the user asks how to protect their MCP servers or set up mcp-pin. Input: app, one of every_app, claude_code, claude_desktop, cursor, vscode, codex, gemini_cli, one_server. Returns the commands or config text for that app and the version they pin. It changes nothing by itself.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | Which app to protect. every_app covers all of them at once. |
No output schema declared.
No examples provided.
mcp_pin_my_servers Servers mcp-pin protects here ~132
List the MCP servers mcp-pin protects on this machine and whether any of them has a change waiting for review. Use it when the user asks which servers are pinned, or after mcp-pin blocked a server. No input. Returns, per server: id, label, tool and prompt counts, the date it was approved, and pending (true when a change is waiting). It never returns definitions or changed text. For a pending change, call mcp_pin_change_summary with its id, then ask the user to run "mcp-pin review <id>" in a terminal to read the diff.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mcp_pin_server_status Public MCP server status ~183
Look up a public MCP server in the signed public log kept by mcp-pin, to see whether its tool definitions have changed and when. Use it before installing or approving an MCP server, or when the user asks if a server changed. Input: query, an npm package name (for example @modelcontextprotocol/server-filesystem) or part of one. Returns up to 5 matching servers, exact name first: name, registry, tool count, first seen date, last change date with the earliest day it could have happened, last successful check, and a link to the full history. Only names, dates and counts are returned, never tool descriptions. An unchanged server is not proof of safety: a server can be hostile from its first version.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | npm package name or part of it, for example "server-filesystem". |
No output schema declared.
No examples provided.
How do I install the mcp-pin server?
mcp-pin runs locally as an npm package, launched with npx -y mcp-pin. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-pin
claude mcp add gautamtalksdev-mcp-pin -- npx -y mcp-pin
What is the mcp-pin server?
mcp-pin is listed in the public MCP registry as io.github.GautamTalksDev/mcp-pin. Check if an MCP server's tool definitions changed after approval, from a signed public log. This page covers its npm package (mcp-pin).
Is the mcp-pin server safe to use?
mcp-pin scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 mcp-pin server expose?
mcp-pin exposes 4 tools: mcp_pin_server_status, mcp_pin_my_servers, mcp_pin_change_summary, mcp_pin_how_to_protect. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Is the mcp-pin server still maintained?
mcp-pin is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the mcp-pin server under?
mcp-pin declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.