Skip to main content
Glama
evo-hydra

Merovingian MCP Server

by evo-hydra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Merovingian MCP Server

No user-submitted related servers found.

    Related Servers

    • coderadius by coderadius-ai

      coderadiusofficial

      coderadius-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query architecture context, data contracts, and blast radius to prevent cross-repo architectural breakage before merging.
      24
      Apache 2.0

    • oss-mcp

      Abbilville
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables cross-repository architecture discovery and dependency routing across multi-service codebases, with automated scanning and batch AST indexing for AI agents to trace request lifecycles and navigate service boundaries.
      10 npm
      MIT

    • Weavatrix

      Weavatrix
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.
      4,912 npm
      4
      MIT

    • servicegraph

      LM20230311
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first cross-service code intelligence engine for AI agents, connecting frontend, gateways, backend services, and databases to enable impact analysis and change planning.
      Apache 2.0

    • MindGraph

      dycm8009
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and analyze code across multiple repositories through a unified knowledge graph, with tools for symbol search, impact analysis, and graph algorithms.
      17 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    The tools are largely distinct, each covering lifecycle stages (register, scan, add_consumer, breaking, impact). The only slight overlap is between `merovingian_consumers` and `merovingian_impact`, as both deal with consumers, but their focus differs (listing consumers vs. full impact assessment).

    Naming Consistency5/5

    All tools follow a consistent `merovingian_<verb>` pattern with clear, descriptive verb choices (e.g., register, scan, add_consumer, breaking, impact). The naming is uniform and predictable.

    Tool Count5/5

    With 10 tools, the count is well-scoped for a contract scanning and dependency analysis server. Each tool covers a distinct step in the workflow without being excessive or sparse.

    Completeness4/5

    The tool surface covers registration, scanning, dependency management, contract listing, breaking change detection, impact analysis, feedback, and audit. Minor gap: no tool to unregister a repository or delete consumer relationships, which could cause dead ends in cleanup scenarios.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources