C-

npm:foundry-zksync-mcp

https://www.npmjs.com/package/foundry-zksync-mcp
70/100 · MCP Trust Grade · checked 3h ago · MCP 0.2.3

What it offers — 21 tools · Developer Tools

init

Scaffold a new foundry project and add [profile.default.zksync] config (forge init)

install

Install dependencies for a foundry project (forge install)

clean

Remove build artifacts (out/ and zkout/) from a foundry project (forge clean)

compile

Compile a foundry-zksync project (forge build --zksync).

test

Run tests in a foundry-zksync project (forge test --zksync).

run_script

Run a forge script targeting zkSync (forge script --zksync)

deploy

Deploy a contract to a zkSync network (forge create --zksync).

verify

Verify a deployed contract on a block explorer (forge verify-contract --zksync).

gas_report

Run tests and generate a gas usage report (forge test --zksync --gas-report).

snapshot

Create or compare gas snapshots (forge snapshot --zksync).

read_foundry_toml

Read and return the contents of foundry.toml from a project.

explain

Explain raw output from foundry-zksync: error messages, logs, or transactions.

cast_abi_encode

ABI-encode values for a given Solidity function/constructor signature (cast abi-encode)

cast_abi_decode

Decode ABI-encoded hex data back into human-readable values (cast abi-decode)

cast_calldata_decode

Decode raw transaction calldata (with 4-byte selector) into function arguments (cast calldata-decode)

cast_call

Read-only call to a deployed contract — no gas spent, no state change (cast call)

cast_send

Send a state-changing transaction to a deployed contract (cast send)

cast_balance

Query the ETH balance of an address (cast balance)

+3 more tools

Spec / packaging20%100
Security (OWASP MCP)30%25
Maintenance / popularity20%75
Tool hygiene15%95
Transparency / provenance15%90

Findings

WARNMCP08 References sensitive file paths / environment secrets.
INFO Static analysis of npm package foundry-zksync-mcp@0.2.3 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:foundry-zksync-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:foundry-zksync-mcp grade C-
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade C- · wmcp.sh
[![MCP Trust Grade C-](https://wmcp.sh/mcp/grade/npm%3Afoundry-zksync-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Afoundry-zksync-mcp)
<a href="https://wmcp.sh/mcp/grade/npm%3Afoundry-zksync-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Afoundry-zksync-mcp/badge.svg" alt="MCP Trust Grade C- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.