Skip to main content
Glama
Sign In
Alberto-Codes

docvet

by Alberto-Codes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to docvet

No user-submitted related servers found.

    Related Servers

    • 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.
      20 npm
      MIT

    • QE-MCP

      mov2day
      F
      license
      Not graded
      quality
      D
      maintenance
      A Python-based MCP server that enforces configurable Quality Assurance automation strategies for AI coding agents, ensuring generated tests adhere to strict architectural and testing standards.
      -

    • Evergreen

      hganumpally-a360
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to read, write, and maintain documentation through an MCP server, providing tools for asking questions, generating docs, checking drift, and exploring knowledge graph.
      48 npm
      MIT

    • mcp_for_agents

      chineidu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables building local, offline MCP servers that expose open-source package documentation to AI agents, with tools to list doc sources, search docs, and retrieve doc content over stdio.
      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.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: docvet_rules is a read-only catalog lookup while docvet_check executes analysis on files. An agent can easily tell which to call for discovery versus execution.

    Naming Consistency4/5

    Both tools share the docvet_ prefix, giving a predictable namespace and readable names. The slight verb/noun mismatch between docvet_rules (noun) and docvet_check (verb) is a minor deviation but still coherent.

    Tool Count3/5

    Two tools is on the thin side for the domain; a linter commonly benefits from separate config, fix, or freshness-context tools. It works but feels under-scoped for the apparent feature set (presence, enrichment, coverage, griffe, freshness).

    Completeness4/5

    Discovery (rules) and execution (check) cover the core linting lifecycle, with rules providing fix guidance. However there is no auto-fix operation despite the emphasis on fix guidance, and freshness/git-context handling is bundled rather than exposed, a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources