Is Protect safe and trustworthy?

tashan scores Protect on public evidence — it is currently abandoned, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Protect?

Don't. This capability has been discontinued by its author or publisher and is not scored or recommended. If you are already running it, `npx tashan-cli doctor` will flag it and name what to move to.

Who maintains Protect?

source: scopeblind/scopeblind-gateway.

‹ The Index

Protect

npm

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

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Security — see all ranked ›

Discontinued — do not install. The author's own notice: “Fail-closed Cedar policy gate + Ed25519 signed receipts for agent tool calls. Denies on any error.” It stays listed so anyone already running it can find this page, and so npx tashan-cli doctor can warn about it. It is not scored and does not appear in any ranking.

solid

“8 worked examples; short of deep on per-tool docs and a stated limitation and setup/auth; read with 1 linked doc(s)”

This grade is wrong ›

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

Instruction depth: 65.0 (solid — documents the job properly, with examples you could follow)
Adoption: 680/wk
Freshness: 79.0
Evidence coverage: 100% of the inputs this score can use
Health: abandoned
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.13.3 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-09-13 protect-mcp now reads as abandoned, was active Upkeep signals stopped, under enough issue pressure that it is not merely finished.
2026-09-13 protect-mcp published 0.13.3, was 0.11.1 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 2 changes to Protect in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

npm ↗ · source ↗ · pkg:protect-mcp

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?