Greenlight
Pre-flight checks for open-source contributions: is this GitHub issue actually landable?
Connector by CloudCorpRecords · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/cloudcorprecords-greenlight
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 9 read · 5 write · 0 delete · 19 not yet classified
- Secrets
- None asked for
- Install scripts
- Not scanned yet
- Runs as
- Node.js package
Tools by what they do 33
Read from the source code; the running server may list different tools.
Read 9 · Look things up without changing anything.
api_statusbabysit_prsbounty_checkcheck_issueci_triageclaim_statusreview_triagescan_repoverify
Write 5 · Create, change, send or run things.
ci_prepclaim_issueshipchecksync_campaignwave_queue
Not yet classified 19 · We could not tell from the name and description.
autopilot_reportcampaign_portfolioclaim_via_apievidence_packguard_prheartbeat_via_apimy_claimsopen_prpassportpr_briefpr_radarpreflight
Show 7 more tools
prep_issueracecheck_issuerepo_digestrepo_frictionscout_campaignverify_commentxray_issues
Files it touches
- Any path the agent passes to its tools
Tools (33)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
api_statusThe hosted Claim Protocol status payload for one issue, read live from the claim API: who holds it, until when, who is queued, and whether the repo honors the protocol. For agents that want the 60-second-fresh answer instead of the 15-minute static one. Read only; no token needed.
autopilot_reportAutopilot in report mode: collects reviews, comments, and check results across your open PRs, verifies bot findings against the code at head, triages CI (introduced vs pre-existing), and returns per-PR items, fix plans, and queued reply drafts. Reads only; never applies fixes or posts comments.
babysit_prsWatch your open PRs and get the one prioritized action list: needs you now (new review findings, CI failing on your code, merge conflicts, new guard flags, stuck checks), waiting on them (checks running, green with no feedback yet), quiet. Compares against stored watermarks so reruns report only what changed since the last check. Cron-friendly: always succeeds unless the input is wrong.
bounty_checkBounty-liveness check for one issue: is the advertised bounty backed by a live platform, an unverifiable claim with no named payer, or a dead platform (algora has been dead since 2025 while thousands of issues still wear its labels)? Returns the classification with its evidence. Context for the contributor, never a verdict. Agent-callable surface of `greenlight bounty`.
campaign_portfolioOne-screen campaign summary: census counts (open/merged/closed), claims by state, the pending posting queue, and the sync drift count. Reads only. For multi-agent campaigns.
check_issueVerdict on whether a GitHub issue is actually landable for an outside contributor. Returns GO, RISKY, TAKEN, GATED, or STALE with reasons, claim signals, and detected repo gates. Call this before writing code for an issue.
ci_prepRun a target repo's own pull_request workflows locally BEFORE opening a PR: discovers .github/workflows triggered on pull_request, executes the mappable run steps (tests, lint, typecheck, build) with per-step timeouts, checks repo conventions (changesets, conventional-commit subjects, DCO sign-off), and reports PASS/FAIL/SKIPPED per check with a GO/NO-GO verdict. Steps that cannot run locally (deploys, secrets, publishes) are SKIPPED with the reason named, never passed. Use after building a fix, before pushing. Local execution only; never touches GitHub.
ci_triageAnswer the red-PR question: is this failure mine or pre-existing? Fetches the failing check runs on the PR head, compares them against the base branch's recent check history, and classifies each failing check as pre-existing, likely-yours, indeterminate (with a stated lean), or external-blocker (deploy/auth failures like Vercel). Call this on any PR with failing CI before spending time debugging.
claim_issuePost a claim comment on a GitHub issue, shaped by the repo's contribution gates. Runs the verdict pipeline first and refuses on TAKEN/STALE verdicts or vouch-gated repos. DRY RUN BY DEFAULT: returns the comment plan without posting unless execute is true, and posting requires GITHUB_TOKEN.
claim_statusThe Claim Protocol pre-flight answer for one issue: who holds it, until when, who is queued, which PRs compete, which gates bite, and whether the repo honors the protocol at all. Returns the SPEC 5.1 status payload with competing PRs and gates merged from the check machinery. The verdict vocabulary matches check_issue (GO / RISKY / TAKEN / GATED / STALE); a null verdict means no protocol claims and the check_issue verdict stands.
claim_via_apiClaim one issue through the hosted claim API. App-aware: when the Greenlight Claims app is installed on the repo the claim goes through the app backend; otherwise it posts as a plain protocol comment and says so. REPORT-MODE SAFE: dry run unless execute is true; executing needs a stored token (greenlight auth login) or the token argument.
evidence_packThe Verified PR evidence pack for one pull request: the guard verdict, CI triage, review triage, and Claim Protocol status of the linked issues, in one markdown document where every claim cites its source (check run, review anchor, claim comment URL). Call this when a maintainer, a recruiter, or your future self needs proof, not a summary.
guard_prMaintainer-side analysis of an incoming pull request: competing fix (other open PRs already fixing the same issue), prior claims by someone other than the PR author, missing required artifacts (changeset file, DCO sign-off, CLA status), and whether the author is a first-time contributor. Returns markdown ready to post as one PR comment plus structured findings. Reads a .greenlight-guard.json in the working directory for per-repo check toggles. Never posts anything. Call this from a GitHub Action or before reviewing an incoming PR.
heartbeat_via_apiRenew one active claim through the hosted claim API (extends the lease). App-aware like claim_via_api. REPORT-MODE SAFE: dry run unless execute is true; executing needs a stored token or the token argument.
my_claimsThe claims babysitter's claim half: bucket every claim in your my-claims registry (~/.greenlight/my-claims.json) by its live Claim Protocol status — linked, linked-dead, healthy-active, heartbeat-due, expiring, unlinked-stale, queue-lost — and retire claims that completed or released. Pair with babysit_prs for the full portfolio picture.
Show 18 more tools
open_prOpen a pull request for an issue from your fork branch. Verifies the branch exists, is ahead of upstream, and (on DCO repos) that every commit carries a Signed-off-by line. Composes the PR title and body (Closes #N plus verdict and gates at open time). DRY RUN BY DEFAULT: returns the composed PR without opening it unless execute is true; opening requires GITHUB_TOKEN.
passportContributor passport for a GitHub login: the claim-ledger account profile, merged PR count, honor ratio, and open claims, returned as markdown plus structured JSON. Agent-callable surface of `greenlight passport`.
pr_briefVerified review brief for ANY pull request (not just your own): what changed grouped by area/risk, CI triage with the base-vs-head classifier, review findings classified real vs false-positive with evidence, test evidence present or explicitly absent, merge-readiness blockers (conflicts, unresolved change requests, missing changesets), ending with a one-line look-at-this-first. Deterministic classifiers only; unverified items are marked as such.
pr_radarMaintainer-side duplicate/competing PR radar for a repo: clusters open PRs working the same issue (closing-strength links) or touching the same files (Jaccard file overlap with title-prefiltered budget). Each cluster reports PR numbers, authors, evidence, and a heuristic suggested-keep pick; unclustered PRs are counted so the picture stays honest. API budget is measured and reported.
preflightThe one-call answer to 'can I work on this issue right now': the Claim Protocol issue status (claim holder, expiry, queue, competing PRs, gates) plus the repo friction summary (how hard this repo is to land a PR in, 0-100). Call this before committing to any issue; it combines claim_status and repo_friction.
prep_issuePrepare to work an issue: check/create your fork and a branch named from the issue title (learning the repo's branch convention from recent PRs when detectable), and write a local PREP.md checklist (verdict, gates, DCO reminders, next commands). Never clones. DRY RUN BY DEFAULT: no fork or branch is created unless execute is true; creating them requires GITHUB_TOKEN.
racecheck_issueKeyword race check for one issue: find open PRs that fix the same problem WITHOUT ever linking the issue, which link-based checks (claims, timelines, X-Ray) cannot see. Extracts the issue's significant problem keywords (filenames like $types.d.ts, identifiers, distinctive terms, quoted phrases), searches and scans the repo's open PRs for overlap, and returns RACE / SUSPECT / CLEAR with per-PR evidence (number, title, author, created date, matched keywords). Field case: sveltejs/kit issue #17465 was raced by PR #17453, which never mentioned the issue. Call this before writing code for an issue …
repo_digestRepo-level maintainer report: what needs attention across the whole repo? Reports PR races (two or more open PRs fixing the same issue, with first-claim arbitration), claimed-by-other conflicts (an open PR whose linked issue was claimed by someone else first), stale claims (issues claimed 14+ days ago with no open PR), and assignment-gate conflicts (repos that require assignment before a PR). Pass a --limit to bound the API budget on large repos; sections that cannot be computed say so instead of showing empty. Call this when triaging a repo, not just one PR.
repo_frictionFriction score 0-100 for a repo (100 = easiest to land an outside PR). Based on detected contribution gates and computed outcome signals.
review_triageTriage the review feedback on your PR: which comments actually need you? Gathers bot (CodeRabbit, cubic, Greptile, Copilot) and human review comments, classifies each finding as likely-real, likely-noise, or needs-decision with the reason stated, and drafts a reply for each. Human reviewer comments are never called noise. Drafts only; nothing is posted. Call this after pushing and getting review feedback.
scan_repoRank a repo's open issues by verdict, GO first. Starts with label-tagged good-first-issue / help-wanted issues; when the repo does not use those labels, falls back to the most recent open unassigned issues (flagged as fallback). Use this to pick a winnable issue instead of a taken one.
scout_campaignCampaign mode: scan repos for winnable issues, rank survivors by friction, merge history, freshness, and verdict strength, and append them to a campaign file as SCOUTED. The campaign file dedupes against everything already claimed or PR'd. Budget-aware: stops with a resume cursor when the API budget is hit.
shipcheckRelease-readiness check for a shipped release: confirms the GitHub release exists, the npm package version is live, the MCP Registry record is active, and the GHCR image tag is published, returning a GO / NO-GO verdict per surface. Agent-callable surface of `greenlight shipcheck`.
sync_campaignReconcile local tracking with the API census: PRs the registry does not know (another agent opened them), state mismatches vs API truth, and stale claims with no PR. Reads only. For multi-agent campaigns where several agents open PRs in parallel.
verifyHonest base-vs-head verification for a checked-out repo: runs the detected test suite at the base ref and at HEAD and reports the red-first delta (newly failing, newly passing), never raw counts. Refuses a dirty working tree unless asked. Agent-callable surface of `greenlight verify`; run it before and after a fix to prove the fix did the work.
verify_commentDraft the verified-finding comment for a maintainer-only repo (modelcontextprotocol/inspector, modelcontextprotocol/servers): outside PRs are closed on sight there, so the contribution that lands is a detailed, verified issue comment. Assembles the comment from your notes: claim, environment, reproduction steps, observed vs expected, root cause, fix sketch, and a verification footer. Sections you leave empty render as explicit gaps, never plausible filler. DRAFT ONLY: nothing is posted, ever. Copy the markdown into the issue thread yourself.
wave_queueBuild queue in one call: filters the Agent Policy Index for winnable open repos, timeline x-rays starter issues with the existing xray engine (CLEAR / RISKY / TAKEN with competing PRs named), excludes repos with behavioral gates (maintainers who reject AI-built PRs in practice), and skips repos where you already have an open PR. Stops with partial results under the API budget floor. Use this to pick what to build today instead of hand-vetting repos.
xray_issuesTimeline X-Ray: deep-verify candidate issues against their GitHub timelines before writing code. Fetches each issue's timeline, classifies every cross-referenced PR with link-strength scoring, and flags reporter-owned fix PRs and comment claims. Returns GO / RISKY / TAKEN per issue with PR evidence (number, state, link strength, URL). List views hide in-flight PRs; run this on scan results first.
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit
- Oct 23, 2026 (6 days ago)
- Last release
- Oct 26, 2026 (3 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
io.github.CloudCorpRecords/greenlight- Version
- 0.22.1
- Auth
- No auth
- Packages
- npm @reneturcios/greenlightoci
ghcr.io/cloudcorprecords/greenlight:0.22.1 - License
- MIT
- Repository
- github.com/CloudCorpRecords/greenlight
- First seen
- Oct 24, 2026
- Last checked
- Oct 26, 2026
More from CloudCorpRecords
- 0.585score
ShelfSignal
CloudCorpRecords
The open store index for AI agents: merchants list real stock, agents find local food and stores.
ConnectorAFreshness: ALocalClaude Code +5 - 0.585score
ProdForge
CloudCorpRecords
Connects MCP servers, packages, security checks, and release gates in one repo.
ConnectorAFreshness: ALocalClaude Code +5 - 0.580score
Logdigest
CloudCorpRecords
Condense a CI log to its failure sections and root-cause lines, with original line anchors.
ConnectorAFreshness: ALocalClaude Code +5 - 0.580score
Agentsfile
CloudCorpRecords
Validate AGENTS.md and CLAUDE.md against repo reality: paths, scripts, and commands checked.
ConnectorAFreshness: ALocalClaude Code +5 - 0.580score
Contextbudget
CloudCorpRecords
Token budget auditor for agent context: per-file estimates, top offenders, exclusion advice.
ConnectorAFreshness: ALocalClaude Code +5 - 0.580score
Envdoc
CloudCorpRecords
Check.env.example against actual env usage in code: missing, stale, and undocumented vars.
ConnectorAFreshness: ALocalClaude Code +5
Cite this page
Greenlight MCP server. Agent Mart. https://agentmart.dev/connectors/cloudcorprecords-greenlight (last updated 2026-10-26)