io.github.bch1212/injectshield
NPM · @INJECTSHIELD/MCP
Prompt-injection firewall for AI agents — scan untrusted text before LLM calls.
Available components
Last scanned (4 hours ago)
Scores higher than 97% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bch1212/injectshield). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 182 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 297 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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/@injectshield/mcp@0.1.4
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 | bch1212/injectshield |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bch1212/injectshield/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.1.4 |
| Rekor log index | 1449629040 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a93bf895b02c7a65b7428b751530156c4d55103dcf5b1e8d5c7ea486ea2086183b3817b8a33d154067a63d3f3d1aca177b90d746435bf711aa4c29648 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
patterns ~32
List supported threat categories, context kinds, and sensitivity levels. Use this to discover what threat_type values scan() can return.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan ~165
Scan text for prompt-injection. Use BEFORE passing any untrusted text (web pages, file contents, user inputs, git commits, tool outputs) into another LLM call. Returns a verdict (safe/unsafe), a confidence score, the threat category, the matched pattern IDs, and an optional sanitized version with injection spans redacted.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Where the text came from. Affects scoring — git commits are treated as more suspicious than user input by default. |
| return_cleaned | boolean | – | Return the input with detected spans redacted. |
| sensitivity | string | – | Detection threshold. low = fewest false positives, high = fewest false negatives. Default: medium. |
| text | string | yes | Text to scan (max 100,000 chars). |
No output schema declared.
No examples provided.
scan_url ~100
Fetch a URL and scan its body for prompt-injection. Useful before feeding scraped page content into another LLM call. Sets the context to web_content automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Override the default web_content context. |
| max_bytes | integer | – | Truncate fetched body before scanning. Default 50000. |
| return_cleaned | boolean | – | – |
| sensitivity | string | – | – |
| url | string | yes | URL to fetch and scan. |
No output schema declared.
No examples provided.
How do I install the io.github.bch1212/injectshield MCP server?
io.github.bch1212/injectshield runs locally as an npm package, launched with npx -y @injectshield/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 · @injectshield/mcp
claude mcp add bch1212-injectshield -- npx -y @injectshield/mcp
What is the io.github.bch1212/injectshield MCP server?
io.github.bch1212/injectshield is an MCP server listed in the public MCP registry as io.github.bch1212/injectshield. Prompt-injection firewall for AI agents, scan untrusted text before LLM calls. This page covers its npm package (@injectshield/mcp).
Is the io.github.bch1212/injectshield MCP server safe to use?
io.github.bch1212/injectshield scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.bch1212/injectshield MCP server expose?
io.github.bch1212/injectshield exposes 3 tools: scan, scan_url, patterns. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.
Is the io.github.bch1212/injectshield MCP server still maintained?
io.github.bch1212/injectshield 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 io.github.bch1212/injectshield MCP server under?
io.github.bch1212/injectshield declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.