Skip to main content
Glama
fabriciopirini

pr-ready-mcp

by fabriciopirini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to pr-ready-mcp

No user-submitted related servers found.

    Related Servers

    • before-you-pr

      b84330808
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent to check a repository's contribution rules (AI policy, CLA/DCO, assignment and claim windows) and an issue's status (linked open, merged and closed PRs, active claims, merge friendliness) before writing any code. It returns a go, comment & claim first, or don't verdict with the rule or PR evidence behind each reason, reading only and never opening PRs or posting comments.
      MIT

    • taken

      RogueAlg0
      A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to check whether a GitHub issue is already taken before volunteering, by analyzing linked PRs, assignees, claimant comments, AI contribution policies, and repo health to return GO, TAKEN, or CAUTION verdicts.
      3
      64 PyPI
      2
      MIT

    • ready-mcp

      SirjanSingh
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to check whether a GitHub issue is ready to hand off before starting work, predicting the files and tests the fix will touch from the live checkout and holding back under-specified issues with a single clarifying question.
      2
      MIT

    • gitworthy

      trippyogi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to scout, rank, and preflight software work before implementation, returning evidence-backed ACT, VERIFY, or SKIP decisions for issues and pull requests.
      74 npm
      2
      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

    A4.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no overlap or ambiguity. Its purpose—verifying PR merge readiness from live GitHub data—is clearly and narrowly defined.

    Naming Consistency5/5

    The sole tool uses a clear snake_case name, pr_readiness, matching the server's purpose. With a single tool there is no inconsistency, and the name is descriptive and predictable.

    Tool Count4/5

    The server has a narrow, single-purpose scope, and the one comprehensive tool earns its place by covering verdicts, reasons, errors, and head-sha verification. A one-tool surface is inherently thin, but it is not trivial or mismatched to the purpose.

    Completeness5/5

    For the domain of PR readiness checking, the tool covers the full lifecycle: verdict states, reason codes with ownership and fixes, expected head SHA, timestamp, and structured errors. No obvious gaps exist for the stated read-only purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources