Ext Ops Panel
Open dashboard
Comparison

com.scopeblind/protect-mcp vs io.github.CloudCorpRecords/actionpin

com.scopeblind/protect-mcp is an MCP server published by scopeblind.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.CloudCorpRecords/actionpin is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
Marketplacecom.scopeblind/protect-mcpio.github.CloudCorpRecords/actionpin
Official MCP Registry Listed
Version: 0.31.1
Downloads/month (npm): 3 791
Downloads/week (npm): 522
Forks (GitHub): 4
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 0.1.7
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.32.1
Downloads/month (npm): 3 791
Downloads/week (npm): 522
Forks (GitHub): 4
Stars (GitHub): 9
Not marked · First seen
Not listed

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

com.scopeblind/protect-mcp vs io.github.CloudCorpRecords/actionpin
Factcom.scopeblind/protect-mcpio.github.CloudCorpRecords/actionpin
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)9 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)2026-10-24 (better)2026-10-23 (worse)
Where it runs (differs)On your machine (protect-mcp)On your machine (@reneturcios/actionpin)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/scopeblind/scopeblind-gatewaygithub.com/cloudcorprecords/actionpin
Changes in the last 7 days (differs)48
First seen (differs)2026-10-112026-10-22

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

com.scopeblind/protect-mcp

In its own words, on Official MCP Registry:

Fail-closed Cedar policy gate + Ed25519 signed receipts for agent tool calls. Denies on any error.

io.github.CloudCorpRecords/actionpin

In its own words, on Official MCP Registry:

GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.

How to run each

com.scopeblind/protect-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio protect-mcp -- npx -y protect-mcp mcp

io.github.CloudCorpRecords/actionpin As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio actionpin -- npx -y @reneturcios/actionpin mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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: com.scopeblind/protect-mcp · What it can do: io.github.CloudCorpRecords/actionpin · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.

Where the data comes from: how the catalog is built