Foundry Zksync MCP Server
foundry-zksync-mcp
npm
v0.2.3
Published by jrigada — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server exposing foundry-zksync CLI tools to AI assistants
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 a deduction.
Findings 12
high Tool "run_script" exposes command/code executionMTC-CAP-001
Tool "run_script" appears to run shell commands or evaluate code (keyword "run_script" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool run_script
high Shell/command execution in server code (dist/tools/anvil_zksync.js)MTC-SRC-002
In the server's implementation (`dist/tools/anvil_zksync.js:2`): 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: ile, spawn } from "node:child_process"; import { promisify } from "node:util"; import { buildEnv } from "./shared.js"; c
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/tools/anvil_zksync.js
high Shell/command execution in server code (dist/tools/cast_abi_decode.js)MTC-SRC-002
In the server's implementation (`dist/tools/cast_abi_decode.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { buildEnv } from "./shared.js"; c
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/tools/cast_abi_decode.js
high Shell/command execution in server code (dist/tools/cast_abi_encode.js)MTC-SRC-002
In the server's implementation (`dist/tools/cast_abi_encode.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { buildEnv } from "./shared.js"; c
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/tools/cast_abi_encode.js
high Shell/command execution in server code (dist/tools/cast_balance.js)MTC-SRC-002
In the server's implementation (`dist/tools/cast_balance.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { buildEnv } from "./shared.js"; c
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/tools/cast_balance.js
high Shell/command execution in server code (dist/tools/cast_call.js)MTC-SRC-002
In the server's implementation (`dist/tools/cast_call.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { buildEnv } from "./shared.js"; c
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/tools/cast_call.js
high Shell/command execution in server code (dist/tools/cast_calldata_decode.js)MTC-SRC-002
In the server's implementation (`dist/tools/cast_calldata_decode.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { buildEnv } from "./shared.js"; c
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/tools/cast_calldata_decode.js
high Shell/command execution in server code (dist/tools/cast_nonce.js)MTC-SRC-002
In the server's implementation (`dist/tools/cast_nonce.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { buildEnv } from "./shared.js"; c
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/tools/cast_nonce.js
high Shell/command execution in server code (dist/tools/cast_send.js)MTC-SRC-002
In the server's implementation (`dist/tools/cast_send.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { walletFields, buildEnv, buildWal
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/tools/cast_send.js
high Shell/command execution in server code (dist/tools/clean.js)MTC-SRC-002
In the server's implementation (`dist/tools/clean.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { profileField, buildEnv } from ".
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/tools/clean.js
high Shell/command execution in server code (dist/tools/compile.js)MTC-SRC-002
In the server's implementation (`dist/tools/compile.js:2`): 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: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { profileField, buildEnv } from ".
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/tools/compile.js
low Mutating tool "run_script" declares no destructiveHintMTC-CAP-005
Tool "run_script" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool run_script
Tools 21
Each tool and what it can reach — statically extracted from the published source.
run_scriptruns code / shellanvil_zksyncno sensitive capabilitycast_abi_decodeno sensitive capabilitycast_abi_encodeno sensitive capabilitycast_balanceno sensitive capabilitycast_callno sensitive capabilitycast_calldata_decodeno sensitive capabilitycast_nonceno sensitive capabilitycast_sendno sensitive capabilitycleanno sensitive capability
Show 11 more tools ↓
compileno sensitive capabilitydeployno sensitive capabilityexplainno sensitive capabilitygas_reportno sensitive capabilityget_zksync_docsno sensitive capabilityinitno sensitive capabilityinstallno sensitive capabilityread_foundry_tomlno sensitive capabilitysnapshotno sensitive capabilitytestno sensitive capabilityverifyno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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 |
|---|---|---|---|---|
v0.2.3 latest |
A 93/100 | 12 | 1.13.0 | 2026-09-07 |
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.
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 foundry-zksync-mcp --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.