dev.weakspot/weakspot vs io.github.Jrigada/foundry-zksync
dev.weakspot/weakspot is an MCP server published by weakspot.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Jrigada/foundry-zksync is an MCP server published by Jrigada. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  dev.weakspot/weakspot |  io.github.Jrigada/foundry-zksync |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 188 Downloads/week (npm): 40 Not marked · First seen |
Listed Version: 0.2.3 Downloads/month (npm): 210 Downloads/week (npm): 44 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | dev.weakspot/weakspot | io.github.Jrigada/foundry-zksync |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (weakspot-mcp) | On your machine (foundry-zksync-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/jrigada/foundry-zksync-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
dev.weakspot/weakspot
Audit Solidity and Rust smart contracts from your editor. Pays per audit in USDC over x402.
io.github.Jrigada/foundry-zksync
Expose foundry-zksync (forge, cast, anvil-zksync) tools for zkSync Era development
How to run each
dev.weakspot/weakspot As a local MCP server: npm package
claude mcp add --env "WEAKSPOT_PRIVATE_KEY=<YOUR_WEAKSPOT_PRIVATE_KEY>" --transport stdio weakspot -- npx -y weakspot-mcpRequires: WEAKSPOT_PRIVATE_KEY (secret)
io.github.Jrigada/foundry-zksync As a local MCP server: npm package
claude mcp add --transport stdio foundry-zksync -- npx -y foundry-zksync-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.Jrigada/foundry-zksync publish no settings it asks for, so we do not compare settings.
What it can do: dev.weakspot/weakspot · What it can do: io.github.Jrigada/foundry-zksync · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.