Smart Contract Security Analyzer
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Smart Contract Security Analyzer (MCP)
A production-ready Model-Context-Protocol (MCP) server that statically audits Solidity contracts for the seven classes of vulnerability most likely to drain your contract — reentrancy, access control, integer overflow, unchecked low-level calls, timestamp dependence, tx.origin authorization, and unprotected selfdestruct.
The server is built on Next.js 14 (App Router) and Vercel's mcp-handler, ships a marketing landing page, an interactive /demo playground, and a direct REST POST /api/analyze endpoint.
Features
Four MCP tools:
analyze_contract,check_vulnerability,generate_audit_report,suggest_fix.Seven AST-based detectors: pure TypeScript walking the
@solidity-parser/parserAST — no Python, no subprocess, no slither on Vercel.Pragma-aware arithmetic detection: only flags overflow on
< 0.8.0contracts (or insideunchecked {}blocks on 0.8+).Risk scoring with cap table: critical 25/cap 50, high 15/cap 30, medium 10/cap 20, low 5/cap 10; clamped 0–100.
Markdown audit report generator: executive summary, findings table, detailed findings, recommendations.
Interactive demo at
/demo: paste a contract, click "Analyze", see a liveRiskScoreand per-findingVulnerabilityCards.Dark theme + purple accent (Tailwind) and copy-to-clipboard install instructions.
Related MCP server: EVM Proxy MCP
Vulnerability coverage
ID | SWC | Detector | Severity | Reference |
reentrancy | SWC-107 | External call before state write | critical | |
access_control | SWC-105 | Public state-mutating function with no | high | |
integer_overflow | SWC-101 | Unsigned arithmetic in pre-0.8 or | high | |
unchecked_calls | SWC-104 | Unwrapped low-level call return value | medium | |
timestamp_dependence | SWC-116 |
| low | |
tx_origin | SWC-115 |
| high | |
selfdestruct | SWC-106 |
| critical |
Quick start (local development)
git clone https://github.com/your-org/smart-contract-mcp.git
cd smart-contract-mcp
npm install
npm run devThen open http://localhost:3000 for the landing page or http://localhost:3000/demo for the interactive playground.
Build & verify
npm run build # type-check + Next.js production build
npm run typecheck # tsc --noEmit
npm run lint # next lint
npm run validate-schemas # exercise the four MCP tool schemasInstall in Claude Desktop
Add the following to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"smart-contract-mcp": {
"url": "https://smart-contract-mcp.vercel.app/api/mcp"
}
}
}Restart Claude Desktop. You can now ask Claude to "audit this contract" or "check this function for reentrancy" and the four tools will be available.
Deploy to Vercel
Push the repo to GitHub.
Import it in Vercel — the default Next.js build command is correct.
No environment variables are required.
The vercel.json in the repo pins the framework to nextjs; @solidity-parser/parser is declared in next.config.ts as an external server-component package so it is not bundled into the client.
API surface
MCP endpoint
GET /api/mcp— list tools + server info.POST /api/mcp— JSON-RPCtools/callinvocations.DELETE /api/mcp— session teardown.
Direct REST
POST /api/analyze—{ source_code, contract_name? }→AnalysisResultJSON.
Source layout
app/ # Next.js App Router (landing, /demo, /api/mcp, /api/analyze)
components/ # Hand-authored UI primitives (Button, Card, Badge, ...)
lib/ # Types, scoring, analyzers/*
scripts/ # smoke-mcp.mjs, validate-schemas.mjs, vulnerable-bank-payload.json
public/og.png # 1200x630 social cardLicense
MIT.
This server cannot be deployed
Maintenance
Related MCP Connectors
The OpenZeppelin Solidity Contracts MCP server integrates OpenZeppelin's security and style rules into AI-driven development workflows, enabling AI assistants to generate safe, correct, and production-ready smart contracts. It automatically validates generated code against OpenZeppelin standards (including imports, modifiers, naming conventions, and security checks) and supports various contract types including ERC-20, ERC-721, ERC-1155, Stablecoins, RWA, Governor, and Account contracts through prompt-driven workflows.
The OpenZeppelin Stylus Contracts MCP server generates secure smart contracts for the Arbitrum Stylus environment using OpenZeppelin templates, including ERC-20, ERC-721, and ERC-1155 standards. It automatically validates generated code against OpenZeppelin's security and style rules, enforcing best practices for imports, modifiers, naming conventions, and security checks to prevent common vulnerabilities. The server integrates with AI development tools like Cursor, Claude, Gemini, Windsurf, and VS Code to enable AI-assisted, production-ready smart contract development.
Audit your MCP servers for poisoned tools and leaked secrets, and check AI-generated code for flaws.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables scanning Solidity smart contracts for 13 vulnerability classes using pattern-based analysis; provides full audit, quick scan, gas analysis, and detector catalog through MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing AI assistants with tools for advanced EVM smart contract analysis, including proxy detection, implementation resolution, and security analysis.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that gives autonomous coding agents deterministic, schema-validated tools for EVM smart contract development — security scanning, gas profiling, compiler diagnostics, and transaction simulation.91MIT
- AlicenseAqualityDmaintenanceAn MCP server that gives AI assistants the ability to check open-source packages for vulnerabilities, enrich findings with real-world exploit intelligence, and statically analyse whether vulnerable code is actually reachable in your project.31Apache 2.0