Skip to main content
Glama
Jrigada

foundry-zksync-mcp

by Jrigada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to foundry-zksync-mcp

No user-submitted related servers found.

    Related Servers

    • foundry-mcp

      maxencerb
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server providing 80+ tools for Foundry Ethereum development, enabling AI assistants to compile, test, deploy smart contracts, interact with EVM chains, and manage local nodes via Forge, Cast, Anvil, and Chisel.
      10 npm
      2
      MIT

    • Prover MCP

      d3lta02
      F
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to control Succinct Prover Network operations on Sepolia testnet, including running provers, calibrating hardware, staking tokens, and monitoring earnings through natural language commands.
      25
      -

    • Foundry MCP Project

      lhemerly
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with Foundry tools through natural language, allowing users to create projects, build contracts, run tests, and manage Ethereum development environments.
      2
      MIT

    • Phantom Secrets MCP Server

      ashlrai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding tools to securely manage secrets via MCP tools for vault operations, diagnostics, and cloud sync, ensuring real keys never enter the LLM context.
      16
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: node management, ABI operations, contract interactions, compilation, deployment, testing, documentation, etc. No two tools overlap in function; even decoding tools differ in input type.

    Naming Consistency4/5

    Tools follow a mix of patterns: some are single verbs (compile, deploy), others are prefixed with 'cast_' for Foundry commands, and a few are descriptive (get_zksync_docs, read_foundry_toml). While not a strict verb_noun pattern throughout, naming is intuitive and predictable.

    Tool Count5/5

    With 21 tools, the server covers the full lifecycle of foundry-zksync development without being overwhelming. Each tool serves a necessary role, and the count is well-scoped for the domain.

    Completeness5/5

    The tool set covers all major operations: project setup, compilation, deployment, testing, gas analysis, script execution, contract interaction, ABI handling, verification, and documentation. No critical gaps are apparent for typical foundry-zksync workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources