Skip to main content
Glama
Sign In
solhint-mcp

solhint-mcp

by vschernoff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to solhint-mcp

No user-submitted related servers found.

    Related Servers

    • llmlint

      la2278647-arch
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to evaluate text or local files for LLM-output quality issues, returning 0-100 scores, grades, and precise line/column findings. It also lets clients list all available lint rules and severities.
      MIT

    • mcp-lint-server

      ZachDreamZ
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server wrapping mcp-lint to perform static analysis and schema checking on other MCP servers.
      MIT

    • mcp-lint-tools

      rog0x
      A
      license
      Not graded
      quality
      D
      maintenance
      Code linting and style checking tools for AI agents, exposed as an MCP server. Supports style checks, naming conventions, complexity analysis, dead code detection, and import analysis.
      50 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    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).

    Naming Consistency5/5

    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.

    Tool Count5/5

    Seven tools is well-scoped for a Solidity linter, covering lint, fix, rule explanation, and config reading without redundancy. Each tool earns its place.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources