Power Strip Security
NPM · POWER-STRIP-SECURITY-MCP · 2 COMPONENTS
Prompt-injection shield for agents: read pages, scan content, audit MCP servers and skills. x402.
Available components
Last scanned (1 hour ago)
Scores higher than 31% 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 Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, reached via @x402/core > zod. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 487 tokens (~121/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.1.0 and 0.2.0: 1 tool removals, 0 breaking changes, 3 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 31 Oct 26 0
- Stability: 0.07 → fail ▼ security
- Schema quality: 94 → 121 ▼ functional
- Tool coverage: 80% → 92% ▲ functional
- Package version: 0.1.0 → 0.2.0 functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 61
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 5 Nov 2026 · Analysed npm/power-strip-security-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 30 |
| 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 →
audit_agent_skill Audit an agent skill or AGENTS.md ~155
Check an agent skill (SKILL.md with its scripts and references) or AGENTS.md, CLAUDE.md, .cursorrules before loading it: prompt injection, curl | bash, encoded commands, credential theft, exfiltration, hardcoded keys, persistence. Paste the files or give one URL. Costs US$0.005 in USDC on Base; nothing is executed.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | The skill files, e.g. [{path: 'SKILL.md', content: '...'}] (max 50, 256 KB) |
| pinned | object | – | Path to fingerprint from a previous audit |
| url | string | – | Or a public URL of one raw text file |
No output schema declared.
No examples provided.
audit_mcp_server Audit an MCP server for tool poisoning ~142
Check an MCP server for tool poisoning before you connect: hidden instructions, secrecy, sensitive-file access, cross-tool shadowing and rug pulls. Pass its URL (its tools are listed read-only, never called) or paste its tools. Optional pinned fingerprints detect changed tools. Costs US$0.01 in USDC on Base; servers that cannot be listed are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | – | Server instructions, if pasting |
| pinned | object | – | Tool name to fingerprint from a previous audit |
| tools | array | – | Or the tools/list result, pasted |
| url | string | – | Streamable HTTP endpoint of the MCP server |
No output schema declared.
No examples provided.
check_prompt_injection Scan content for prompt injection ~97
Scan HTML or text you already have (an email, a document, a tool result) for prompt injection. Returns the risk report and the cleaned text wrapped as untrusted data. Costs US$0.002 in USDC on Base. Max 256 KB.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The HTML or text to scan |
| format | string | – | – |
| url | string | – | Where the content came from (optional) |
No output schema declared.
No examples provided.
read_url Read a web page safely ~93
Fetch a public web page and return it as clean markdown with hidden text, invisible characters and data-exfiltration links removed, plus a prompt-injection risk report. Costs US$0.005 in USDC on Base; pages that cannot be read are not charged. Respects robots.txt.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | markdown keeps links; text drops them |
| url | string | yes | Public http(s) URL |
No output schema declared.
No examples provided.
How do I install the Power Strip Security MCP server?
Power Strip Security runs locally as an npm package, launched with npx -y power-strip-security-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · power-strip-security-mcp
claude mcp add albertbalestrini-power-strip-security -- npx -y power-strip-security-mcp
What is the Power Strip Security MCP server?
Power Strip Security is an MCP server listed in the public MCP registry as io.github.AlbertBalestrini/power-strip-security. Prompt-injection shield for agents: read pages, scan content, audit MCP servers and skills. x402. This page covers its npm package (power-strip-security-mcp).
Is the Power Strip Security MCP server safe to use?
Power Strip Security scores 62 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Power Strip Security MCP server expose?
Power Strip Security exposes 4 tools: read_url, check_prompt_injection, audit_mcp_server, audit_agent_skill. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.
Is the Power Strip Security MCP server still maintained?
Power Strip Security is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Power Strip Security MCP server under?
Power Strip Security declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.