Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.bch1212/injectshield

NPM · @INJECTSHIELD/MCP · SCANNED AUG 3

Prompt-injection firewall for AI agents — scan untrusted text before LLM calls.

Available components

npm · @injectshield/mcp 78
+33 this week 78 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 88 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @injectshield/mcp

# add to Claude Code
claude mcp add bch1212-injectshield -- npx -y @injectshield/mcp
# add to Codex CLI
codex mcp add bch1212-injectshield -- npx -y @injectshield/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bch1212-injectshield": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@injectshield/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bch1212-injectshield --command npx --arg -y --arg @injectshield/mcp
# ~/.hermes/config.yaml
mcp_servers:
  bch1212-injectshield:
    command: "npx"
    args: ["-y", "@injectshield/mcp"]
// mcp.json
{
  "mcpServers": {
    "bch1212-injectshield": {
      "command": "npx",
      "args": [
        "-y",
        "@injectshield/mcp"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +52
    • Provenance: unverified → pass ▲ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • The attested source repository moved: bch1212/injectshield security
    • Capabilities: pass → unverified ▼ functional
    • Maintenance: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • License: unverified → pass ▲ functional
    • Schema quality: unverified → good ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 +20
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −39
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 45

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@injectshield/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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:
https://slsa.dev/provenance/v1
Subject digest:
sha512:a93bf895b02c7a65b7428b751530156c4d55103dcf5b1e8d5c7ea486ea2086183b3817b8a33d154067a63d3f3d1aca177b90d746435bf711aa4c29648
Discovery method:
attestation_endpoint
Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 3 exposed · ~297 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
contextstring—Where the text came from. Affects scoring — git commits are treated as more suspicious than user input by default.
return_cleanedboolean—Return the input with detected spans redacted.
sensitivitystring—Detection threshold. low = fewest false positives, high = fewest false negatives. Default: medium.
textstringyesText 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.

NameTypeReqDescription
contextstring—Override the default web_content context.
max_bytesinteger—Truncate fetched body before scanning. Default 50000.
return_cleanedboolean——
sensitivitystring——
urlstringyesURL to fetch and scan.

No output schema declared.

No examples provided.