# @reneturcios/greenlight Pre-flight and coordination layer for open-source contribution: issue verdicts, Timeline X-Ray, PR radar and review briefs. CLI + MCP server. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the package rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 0.19.0 - **Author:** io.github.CloudCorpRecords - **License:** MIT - **npm:** @reneturcios/greenlight - **Source:** https://github.com/CloudCorpRecords/greenlight - **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport) ## Trust 60/100 (B), scored on the package rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-10-21T01:32:28.730Z - **Version scanned:** 0.20.0 - **CVEs:** none found by OSV at scan time **Changes since the previous scan:** tool-added ## Tools 33 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `check_issue` — Verdict on whether a GitHub issue is actually landable for an outside contributor. Returns GO, RISKY, TAKEN, GATED, or STALE with reasons, claim signals, and de - `scan_repo` — Rank 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 b - `xray_issues` — Timeline X-Ray: deep-verify candidate issues against their GitHub timelines before writing code. Fetches each issue's timeline, classifies every cross-reference - `racecheck_issue` - `repo_friction` — Friction score 0-100 for a repo (100 = easiest to land an outside PR). Based on detected contribution gates and computed outcome signals. - `wave_queue` — Build 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 / T - `verify` — Honest 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 - `shipcheck` — Release-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 G - `passport` — Contributor passport for a GitHub login: the claim-ledger account profile, merged PR count, honor ratio, and open claims, returned as markdown plus structured J - `bounty_check` — Bounty-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 h - `claim_issue` — Post 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-ga - `prep_issue` — Prepare 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) - `open_pr` — Open 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- - `ci_triage` — Answer 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 - `review_triage` — Triage the review feedback on your PR: which comments actually need you? Gathers bot (CodeRabbit, cubic, Greptile, Copilot) and human review comments, classifie - `guard_pr` — Maintainer-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 au - `repo_digest` — Repo-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 arbitra - `claim_status` — The 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 th - `preflight` — The 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 f - `verify_comment` — Draft the verified-finding comment for a maintainer-only repo (modelcontextprotocol/inspector, modelcontextprotocol/servers): outside PRs are closed on sight th - `babysit_prs` — Watch 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, stuc - `evidence_pack` — The 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 - `scout_campaign` - `my_claims` - `sync_campaign` - `campaign_portfolio` - `autopilot_report` - `api_status` - `claim_via_api` - `heartbeat_via_api` - `ci_prep` - `pr_radar` - `pr_brief` ## Install **Verdict: review** — Installable, but 2 things to check first: 1 suspicious change since the previous scanned version. **Cautions** (coverage gaps and advisories — never blocking) - 1 suspicious change since the previous scanned version. — Tool surface grew since v0.19.0: added racecheck_issue - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"greenlight\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@reneturcios/greenlight\"\n ]\n }\n }\n}" ``` ## Blast radius Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface. - Floor 13, ceiling 31 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/%40reneturcios%2Fgreenlight - Install plan: https://forgeregistry.com/api/v1/packages/%40reneturcios%2Fgreenlight/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/%40reneturcios%2Fgreenlight - HTML page: https://forgeregistry.com/registry/%40reneturcios%2Fgreenlight - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.