MCP Smart Contract Analyst
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze-verified-contractC | Analyze a verified contract from an address on the Monad testnet. |
| analyze-unverified-contractC | Analyze a unverified contract from an address on the Monad testnet. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.