Bridge (aiwerk) MCP Server

@aiwerk/mcp-bridge npm v3.0.2

Published by @aiwerk — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
B
87/100
Last scanned
Trust
B · 87/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
B Why this grade 100 − 12.6 = 87/100

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:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection
−6.3 Package runs install-time scripts MTC-SUP-010 supply-chain

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.

Findings 9

high Shell/command execution in server code (dist/bin/mcp-bridge.js)MTC-SRC-002

In the server's implementation (`dist/bin/mcp-bridge.js:6`): 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 dist/bin/mcp-bridge.js

high Shell/command execution in server code (dist/src/cli-auth.js)MTC-SRC-002

In the server's implementation (`dist/src/cli-auth.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 dist/src/cli-auth.js

high Shell/command execution in server code (dist/src/transport-stdio.js)MTC-SRC-002

In the server's implementation (`dist/src/transport-stdio.js:1`): 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 dist/src/transport-stdio.js

high Shell/command execution in server code (dist/src/update-checker.js)MTC-SRC-002

In the server's implementation (`dist/src/update-checker.js:1`): 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 dist/src/update-checker.js

high Shell/command execution in server code (scripts/postinstall.cjs)MTC-SRC-002

In the server's implementation (`scripts/postinstall.cjs:18`): 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/postinstall.cjs

medium Hardcoded egress to an external endpoint (dist/src/embeddings.js)MTC-SRC-003

In the server's implementation (`dist/src/embeddings.js:70`): 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("https://api.openai.com/v1/embeddings"

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 dist/src/embeddings.js

medium Hardcoded egress to an external endpoint (dist/src/oauth2-credentials-file.js)MTC-SRC-003

In the server's implementation (`dist/src/oauth2-credentials-file.js:59`): 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("https://www.googleapis.com/oauth2/v2/userinfo"

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 dist/src/oauth2-credentials-file.js

medium Untrusted input concatenated into a command sink (dist/bin/mcp-bridge.js)MTC-SRC-009

In the server's implementation (`dist/bin/mcp-bridge.js:224`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`which ${

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 dist/bin/mcp-bridge.js

medium Package runs install-time scripts (postinstall)MTC-SUP-010

"@aiwerk/mcp-bridge" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package @aiwerk/mcp-bridge

What this scan could not see

Versions

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.

VersionScoreFindingsEngineScanned
v3.0.2 latest B 87/100 9 1.5.0 2026-07-23

Embed this score

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.

MCP Trust Score: B · 87/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/aiwerk-mcp-bridge/badge.svg)](https://mcptrustchecker.com/registry/aiwerk-mcp-bridge)
HTML
<a href="https://mcptrustchecker.com/registry/aiwerk-mcp-bridge"><img src="https://mcptrustchecker.com/registry/aiwerk-mcp-bridge/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/aiwerk-mcp-bridge/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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 @aiwerk/mcp-bridge --online

Use the free API → How scoring works

Other implementations of Bridge 9

Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →

More in Other