zk-circuit-auditor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CYSIC_MODEL | No | Model id. | minimax-m3 |
| CYSIC_API_KEY | No | Bearer token for the Cysic API. If not provided, server falls back to offline rule-based auditor. | |
| CYSIC_BASE_URL | No | OpenAI-compatible base URL. | https://token-ai.cysic.xyz/v1 |
| CYSIC_TIMEOUT_MS | No | Per-request timeout in milliseconds. | 60000 |
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 |
|---|---|
| audit_circuitA | Audit a ZK circuit (Circom, Noir, or Halo2) for soundness and constraint bugs. Returns structured findings, a summary, and a 0-100 soundnessScore. Each finding is tagged with a ZK Weakness Classification id (ZKWC-001..015). |
| check_constraintA | Targeted check for a single reviewer's concern (e.g. 'is the output |
| explain_circuitA | Plain-English explanation of a ZK circuit: what it proves, its public/private signals, and a signal -> constraint map. Useful for onboarding reviewers. |
| suggest_constraintsA | Propose the minimal set of additional constraints (or, in Noir/Halo2, code-level additions) to make the circuit sound. Returns code snippets tagged with ZK Weakness Classification ids. |
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: full audit, targeted constraint check, circuit explanation, and constraint suggestion. There is no overlap or ambiguity.
All tool names follow the consistent verb_noun pattern with snake_case (audit_circuit, check_constraint, explain_circuit, suggest_constraints), making them predictable and easy to remember.
With 4 tools, the server is well-scoped for its purpose of ZK circuit auditing. Each tool covers a distinct aspect without unnecessary redundancy or gaps.
The toolset covers the core auditing workflow: full audit, targeted checks, explanation, and constraint suggestions. A minor gap is the lack of a dedicated tool to list or explain the weakness classifications referenced in results, but the core operations are complete.