Skip to main content
Glama
sspcodeflix

woodpecker-mcp

by sspcodeflix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to woodpecker-mcp

No user-submitted related servers found.

    Related Servers

    • code-graph

      osadan
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying cross-repo code dependencies, HTTP routes, database tables, and queues via an MCP server using Cypher queries.
      -
    • Ravenroot Second Brain MCP by ravenroot-ai

      Ravenroot Second Brain MCPofficial

      ravenroot-ai
      A
      license
      A
      quality
      C
      maintenance
      Runs a local, read-only knowledge graph over MCP, enabling graph queries, path finding, explanations, neighbor exploration, statistics, and god-node discovery without cloud dependencies.
      10
      Apache 2.0

    • procurement-graph

      mfbaig35r
      A
      license
      A
      quality
      D
      maintenance
      Exposes a dependency graph of strategic sourcing artifacts and analyses as an MCP server, enabling navigation of phases, analyses, deliverables, and graph traversal for impact analysis and build order.
      16
      Apache 2.0

    • Reachable

      DevAnuragT
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes the code-and-dependency graph over MCP so clients can list and explain CVE findings from public endpoints, find supply-chain hubs, recommend and plan upgrades, verify a fix in a rebuilt scratch graph, and propose a draft fix PR. Queries are read-only and no tool executes an action.
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct role: detecting blind spots, diagnosing root causes, computing blast radius, providing service health, and retrieving topology. Minimal overlap, clear boundaries.

    Naming Consistency5/5

    All tools follow a consistent 'woodpecker_verb_noun' pattern using snake_case, e.g., woodpecker_detect_blind_spots, woodpecker_get_topology. No deviations.

    Tool Count5/5

    With 5 tools covering topology, health, blind spots, root cause, and blast radius, the set is well-scoped for diagnostic purposes without being excessive or thin.

    Completeness5/5

    The set provides a complete workflow for service dependency analysis: establish topology, check health, detect blind spots, find root cause, and compute blast radius. No obvious gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources