solhint-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 |
|---|---|
| lint_solidityA | Lint a Solidity source string with the project or supplied Solhint config. |
| lint_fileB | Lint one Solidity file inside this server instance project. |
| lint_projectC | Lint Solidity files in this server instance project. |
| fix_solidityA | Apply Solhint autofixes to a Solidity source string and return the corrected source. Does not touch any file. |
| fix_fileA | Apply Solhint autofixes to one Solidity file. Previews the result by default; pass write: true to save it. |
| explain_ruleA | Explain a known Solhint rule and suggest a correction. |
| get_configA | Read the Solhint config for this server instance project. |
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 7 tools
Tools are cleanly split along two axes: action (lint vs fix) and target (source string, single file, project), plus explain_rule and get_config which are clearly unique. The main potential confusion is lint_file vs lint_project, but descriptions clarify scope (one file vs all files).
All tools follow a consistent verb_noun snake_case pattern: lint_*, fix_*, explain_rule, get_config. The target suffixes (solidity/file/project) are used predictably across lint_* and fix_* pairs.
Seven tools is well-scoped for a Solidity linter, covering lint, fix, rule explanation, and config reading without redundancy. Each tool earns its place.
The surface covers linting (string/file/project), autofixing (string/file), rule explanation, and config reading. A project-wide fix (fix_project) and a way to list available rules are minor gaps, but core workflows are covered.