Skip to main content
Glama
MCP Smart Contract Analyst

MCP Smart Contract Analyst

by RockYuan

MCP Smart Contract Analyst / 智能合约分析器

@author Ry @RockRockDay

Implements a Model Context Protocol (MCP) server to interact with the Monad blockchain for smart contract source code analysis, including functionality and security evaluation.

实现了一个 Model Context Protocol (MCP) 服务器,用于与 Monad 区块链交互,进行智能合约源代码的功能性与安全性分析。

For unverified contracts, decompilation is used to assist in source code recovery and review.

对于未验证的合约,将尝试进行反编译以辅助恢复和审查源代码。

What is MCP? / 什么是 MCP?

The Model Context Protocol (MCP) is a standard that allows AI models to interact with external tools and services.

Model Context Protocol(模型上下文协议,简称 MCP)是一种标准,允许 AI 模型与外部工具和服务进行交互。

Related MCP server: Monad MCP Server

Prerequisites

  • Node.js (v16 or later)

  • npm or yarn

  • Claude Desktop / Cursor ide / more...

Getting Started

  1. Clone this repository

git clone https://github.com/rockyuan/mcp-contract-analyst.git
  1. Install dependencies:

npm install
  1. Build the project

npm run build

The server is now ready to use!

Adding the MCP server to Cursor

  1. Open "Cursor".

  2. Open Settings.

Cursor > Settings > Cursor Settings > MCP

  1. Click "Add a new global MCP server".

  2. Add details about the MCP server and save the file.

{
  "mcpServers": {
    "mcp-contract-analyst": {
      "command": "node",
      "args": ["/<path-to-project>/build/index.js"],
      "env": {
        "API_URL": "https://api.blockvision.org/v2/monad/contract/source/code?address=",
        "API_KEY": "xxxxxxxxxxx",
        "DECOMPILE_URL": "https://www.ethervm.io/decompile"
      }
    }
  }
}
  1. Refresh Cursor.

Using the MCP server

Adding the MCP server to Claude Desktop

  1. Open "Claude Desktop"

  2. Open Settings

Claude > Settings > Developer

  1. Open claude_desktop_config.json

  2. Add details about the MCP server and save the file.

{
  "mcpServers": {
    "mcp-contract-analyst": {
      "command": "node",
      "args": ["/<path-to-project>/build/index.js"],
      "env": {
        "API_URL": "https://api.blockvision.org/v2/monad/contract/source/code?address=",
        "API_KEY": "xxxxxxxxxxx",
        "DECOMPILE_URL": "https://www.ethervm.io/decompile"
      }
    }
  }
}
  1. Restart "Claude Desktop"

Further Resources

Thanks

Available Tools

2 tools
analyze-unverified-contractC

Analyze a unverified contract from an address on the Monad testnet.

Inputs: address (required).

analyze-verified-contractC

Analyze a verified contract from an address on the Monad testnet.

Inputs: address (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one analyzes unverified contracts and the other analyzes verified contracts on the Monad testnet. There is no overlap or ambiguity between them, as the verification status is a binary distinction that cleanly separates their use cases.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'analyze' as the verb and descriptive adjectives ('unverified', 'verified') modifying the noun 'contract'. The naming is perfectly uniform and predictable across the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a 'Smart Contract Analyst' domain. While the tools cover analysis of both verified and unverified contracts, the scope suggests potential for more analytical operations (e.g., security checks, gas estimation, function analysis), making the current count insufficient for comprehensive analysis.

    Completeness2/5

    The server is severely incomplete for smart contract analysis. It only provides basic analysis based on verification status, missing essential operations like vulnerability scanning, gas optimization suggestions, code complexity metrics, or interaction with contract functions. This limited surface will likely cause agent failures when deeper analysis is required.

    Related MCP Connectors

    Related MCP Servers