Skip to main content
Glama
verdochello

verdoc-mcp

by verdochello
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to verdoc-mcp

No user-submitted related servers found.

    Related Servers

    • Cartograph

      anthony-maio
      A
      license
      Not graded
      quality
      C
      maintenance
      Analyzes repositories and generates task-focused context packets for coding agents, with tools for repo analysis, file contents, and task packet construction.
      30
      3
      MIT

    • codebase-doctor

      jordan-chris191
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with structured, deterministic repository intelligence—file tree, dependencies, hotspots, and git history—via Model Context Protocol, enabling them to understand codebases without reconstructing architecture from scratch.
      1
      MIT

    • openkrak-mcp

      FrnzJulianBergmann
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to pre-compute repository structure and access structured intelligence briefs, including dependency graphs, hotspots, and blast radius, reducing token usage and improving code understanding.
      1,995
      1
      -

    • FixMap

      aryamthecodebreaker
      A
      license
      Not graded
      quality
      A
      maintenance
      Deterministic, local-first repository context for coding agents. Maps an issue, prompt, or git diff to ranked files to read first, likely test commands, and review-risk notes—no API key required.
      19
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have distinct outputs: one generates an AGENTS.md file, the other returns structured facts and a score. There is some overlap in the underlying data (toolchain, directory layout), but the purpose and return type are clear enough to avoid serious confusion.

    Naming Consistency3/5

    Both tools share the 'verdoc_' prefix, but the suffixes are inconsistent: 'agents_md' is a noun-phrase while 'scan' is a verb. They are readable and predictable, but not a strict verb_noun pattern.

    Tool Count3/5

    With only two tools, the server feels thin, but it is scoped to a narrow domain (analyzing GitHub repos). The small count is not unreasonable, though it leaves room for more related tools.

    Completeness4/5

    The domain is repository analysis, and the two tools cover the core operations: generating an AGENTS.md guide and performing a detailed scan. Minor gaps exist (e.g., no direct metadata-only fetch), but for the stated purpose the surface is reasonably complete.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources