mcp-pin vs MCP Verify
mcp-pin is an MCP server published by GautamTalksDev. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Verify is an MCP server published by sentinelsignal.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  mcp-pin | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.4 Downloads/month (npm): 689 Downloads/week (npm): 266 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 1.0.269 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | mcp-pin | MCP Verify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-31 | Not published |
| Where it runs (differs) | On your machine (mcp-pin) | Remote server (verify.sentinelsignal.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/gautamtalksdev/mcp-pin | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | No HTTP response at the last check (21 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
mcp-pin
Check if an MCP server's tool definitions changed after approval, from a signed public log.
MCP Verify
Trust, freshness, policy, and discovery layer for public MCP servers.
How to run each
mcp-pin As a local MCP server: npm package
claude mcp add --transport stdio mcp-pin -- npx -y mcp-pin lookupMCP Verify As a remote MCP server
claude mcp add --transport http verify https://verify.sentinelsignal.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only MCP Verify has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: mcp-pin · What it can do: MCP Verify · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.