InjectShield (bch1212/injectshield) is an MCP server listed on the M8ven Trust Index. It scores 40 out of 100, grade D. It declares 3 tools. No publisher has claimed this listing.

D
Caution
40/100

InjectShield

Prompt-injection firewall for AI agents that scans untrusted text before LLM calls.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

bch1212

Source: PulseMCP · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
5 flows detected: API_BASE_URL, INJECTSHIELD_API_BASE, STRIPE_TEST_SECRET_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 5 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 7 credentials: ADMIN_TOKEN, ANTHROPIC_API_KEY, INJECTSHIELD_API_KEY, SENDGRID_API_KEY, STRIPE_SECRET_KEY, STRIPE_TEST_SECRET_KEY, STRIPE_WEBHOOK_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical5 high25 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@1.6.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@1.6.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

highhono@4.4.7GHSA-3vhc-576x-3qv4

Hono JWK Auth Middleware has JWT algorithm confusion when JWK lacks "alg" (untrusted header.alg fallback)

highhono@4.4.7GHSA-88fw-hqm2-52qc

hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard

highhono@4.4.7GHSA-f67f-6cw9-8mq4

Hono JWT Middleware's JWT Algorithm Confusion via Unsafe Default (HS256) Allows Token Forgery and Auth Bypass

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configADMIN_EMAIL
🔐 secretADMIN_TOKEN
configALERT_THRESHOLD
🔐 secretANTHROPIC_API_KEY
configAPI_BASE_URL
configDISCORD_WEBHOOK_URL
configENVIRONMENT
configGITHUB_CLASSIC_PAT
configINJECTSHIELD_API_BASE
🔐 secretINJECTSHIELD_API_KEYclaude mcp add injectshield --env =is_live_… -- npx -y @injectshield/mcp
configINJECTSHIELD_TEST
configPUBLIC_BASE_URL
🔐 secretSENDGRID_API_KEY
configSIGNUP_FROM_EMAIL
configSIGNUP_FROM_NAME
configSTRIPE_PRICE_HOBBY
configSTRIPE_PRICE_PRO
configSTRIPE_PRICE_TEAM
🔐 secretSTRIPE_SECRET_KEY
🔐 secretSTRIPE_TEST_SECRET_KEY
🔐 secretSTRIPE_WEBHOOK_SECRET
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/3 tools missing one or more hints — scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scan_url (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); patterns (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

1/3 tools referenced in tests (33%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets stay with their owner

2 secret/sensitive values flow into network calls (API_BASE_URL → dynamic, API_BASE_URL → api.stripe.com) (3 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

5 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 5 high severity in production deps — hono@4.4.7 (high), hono@4.4.7 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 9 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/bch1212/injectshield?variant=verified)](https://m8ven.ai/mcp/bch1212/injectshield)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ec8eb5b2c863002bf19514f83155835768416eb8
code hash: e44a6fb951a49bd481672afdaabd2e9466217ddff42e1465a8d4b5d5c25d34f5
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client