@e0ipso/drupal-bridge-mcp
npm
v2.1.2
Published by @e0ipso — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −40.7 | Hardcoded JSON Web Token in server code ×4 MTC-SRC-008 | exfiltration |
Grade capped: 4 confirmed high findings → grade capped at D. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind the deduction.
A live-looking JSON Web Token is hardcoded in `dist/oauth/__tests__/jwt-decoder.test.js:6`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: JSON Web Token: eyJh…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server dist/oauth/__tests__/jwt-decoder.test.js
A live-looking Stripe secret key is hardcoded in `dist/utils/__tests__/logger.test.js:174`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: Stripe secret key: sk_l…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server dist/utils/__tests__/logger.test.js
A live-looking JSON Web Token is hardcoded in `src/oauth/__tests__/jwt-decoder.test.ts:9`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: JSON Web Token: eyJh…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server src/oauth/__tests__/jwt-decoder.test.ts
A live-looking Stripe secret key is hardcoded in `src/utils/__tests__/logger.test.ts:264`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: Stripe secret key: sk_l…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server src/utils/__tests__/logger.test.ts
In the server's implementation (`.ai/task-manager/config/scripts/check-task-dependencies.cjs:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .ai/task-manager/config/scripts/check-task-dependencies.cjs
In the server's implementation (`scripts/lint-staged-eslint.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/lint-staged-eslint.js
In the server's implementation (`tests/integration/oauth-metadata-discovery.test.ts:101`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(
`http://${TEST_HOST}:${TEST_PORT}/health`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/integration/oauth-metadata-discovery.test.ts
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1.2 latest |
F 59/100 | 7 | 1.5.0 | 2026-07-22 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @e0ipso/drupal-bridge-mcp --online
Security scan results for the Actors MCP server.
Security scan results for the Agentmemory MCP server.
Security scan results for the Agents MCP server.
Security scan results for the Ansible Drupal MCP server.
Security scan results for the Anthrop Api MCP server.
Security scan results for the Better Notion MCP server.