MCP Sourcify MCP Server

Most developer tooling work still happens through a UI a human drives. MCP Sourcify MCP server moves it into the conversation instead. MCP server for interacting with Sourcify API.

The short version

A Model Context Protocol (MCP) server that provides tools for interacting with the Sourcify API to verify and retrieve smart contract source code.

This MCP server enables LLMs to interact with Sourcify, a decentralized repository of verified smart contract source code. It provides tools to check contract verification status, retrieve source code, and access contract metadata across multiple blockchain networks.

• Check Contract Verification — Verify if a contract is registered on Sourcify
• Get Contract Source — Retrieve the complete source code of verified contracts
• Get Contract Metadata — Access compiler settings and ABI information
• Batch Verification — Check multiple contracts in a single request

What it needs from you

Configuration is passed through the environment: SOURCIFY_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by soyrubio; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.