recon-fuzz-chimera-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scaffold_projectB | Scaffold a complete Chimera fuzzing test suite for a given contract and its functions. Returns an array of {path, content} for all project files. |
| generate_propertiesC | Generate 8-15 curated invariant properties with Solidity skeletons based on the protocol type and contract source. |
| get_templateB | Get a complete ready-to-compile Chimera project template for a standard protocol type. |
| explain_patternB | Get a detailed explanation of a Chimera fuzzing pattern with code examples. |
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 4 tools
Each tool has a clearly distinct purpose: explain_pattern provides documentation, generate_properties creates invariants, get_template offers project templates, and scaffold_project builds test suites. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming follows a consistent verb_noun pattern (e.g., explain_pattern, generate_properties) with minor deviations: get_template uses 'get' instead of a more descriptive verb like 'fetch' or 'retrieve', but this is a small inconsistency that does not hinder readability or predictability.
With 4 tools, the server is well-scoped for its purpose of Chimera fuzzing support. Each tool earns its place by covering distinct aspects of the workflow: documentation, property generation, templating, and project scaffolding, without being overly sparse or bloated.
The tool set covers key stages of fuzzing setup: learning (explain_pattern), planning (generate_properties), templating (get_template), and implementation (scaffold_project). A minor gap exists in runtime or execution tools (e.g., run_fuzzer, analyze_results), but agents can work around this by using the generated projects externally.