Oregon Code vs Solhint MCP
A side-by-side look at the Oregon Code and Solhint MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Solhint MCPLegal · Local subprocess (stdio)MCP server for Solhint — lint and autofix Solidity smart contracts from any MCP client53GoodAuth: no auth requiredVerdict: choose Oregon Code for legal work as a local process; choose Solhint MCP for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Oregon Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
SChoose Solhint MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
lint_solidity, lint_file, lint_project.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Solhint MCP | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 41/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Oregon Code tools
No tool names declared yet. Check the project README from the listing page.
Solhint MCP tools 7
lint_solidityLint a Solidity source stringlint_fileLint one `.sol` file inside the projectlint_projectLint a project-relative globfix_solidityAutofix a Solidity source stringfix_fileAutofix one `.sol` fileexplain_ruleExplain any rule the linter shipsget_configShow the project's Solhint config
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Oregon Code
{
"mcpServers": {
"oregon-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-oregon-code"
]
}
}
}
Solhint MCP
{
"mcpServers": {
"solhint-mcp": {
"command": "npx",
"args": [
"-y",
"solhint-mcp"
]
}
}
}
Frequently asked questions
Oregon Code is categorized under Legal and uses a local stdio subprocess. Solhint MCP belongs to Legal and uses a local stdio subprocess. Pick Oregon Code for legal work and Solhint MCP for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Oregon Code has no declared pricing — check the project's own site. Solhint MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add oregon-code and solhint-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Oregon Code has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Solhint MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.