putty
MCPBlockchainRPC

is_contract_verified

Check whether a contract address is verified on Sourcify, and report the match status (full match, exact byte-for-byte match, or unverified). Returns the minimal record — match type, runtime/creation match, and the verification timestamp — without pulling sources or ABI. Use this as a gate before calling `get_contract_source_files`; a 404 here means the contract is not on Sourcify and the file-fetch tool will not have anything to return.

Check whether a contract address is verified on Sourcify, and report the match status (full match, exact byte-for-byte match, or unverified).

Input

The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.

Calling it

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "is_contract_verified", "arguments": {} }
}

Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.

Notes

Returns the minimal record — match type, runtime/creation match, and the verification timestamp — without pulling sources or ABI. Use this as a gate before calling get_contract_source_files; a 404 here means the contract is not on Sourcify and the file-fetch tool will not have anything to return.

The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.

On this page