Pre-flight and coordination layer for open-source contribution: issue verdicts, Timeline X-Ray, PR radar and review briefs. CLI + MCP server.
Inferido de los transportes que declara este listado (stdio). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.
La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.
Leído del código que npm publica realmente, en el momento del análisis. El paquete nunca se ejecutó. Las herramientas registradas dinámicamente en tiempo de ejecución, o escondidas en código empaquetado o minificado, pueden pasarse por alto — así que esto es un mínimo de la superficie de herramientas, no un censo completo.
racecheck_issue.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.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 detected repo gates. Call this before writing code for an issue.
No se publicó ningún esquema de entrada para esta herramienta.
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.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 back to the most recent open unassigned issues (flagged as fallback). Use this to pick a winnable issue instead of a taken one.
No se publicó ningún esquema de entrada para esta herramienta.
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…Timeline 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…
No se publicó ningún esquema de entrada para esta herramienta.
racecheck_issuenueva desde la v0.19.0Sin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
repo_frictionFriction score 0-100 for a repo (100 = easiest to land an outside PR). Based on detected contribution gates and computed outcome signals.Friction score 0-100 for a repo (100 = easiest to land an outside PR). Based on detected contribution gates and computed outcome signals.
No se publicó ningún esquema de entrada para esta herramienta.
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 whe…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 / TAKEN with competing PRs named), excludes repos with behavioral gates (maintainers who reject AI-built PRs in practice), and skips repos whe…
No se publicó ningún esquema de entrada para esta herramienta.
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…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, newly passing), never raw counts. Refuses a dirty working tree unless asked. Agent-callable surface of `greenlight verify`; run it before…
No se publicó ningún esquema de entrada para esta herramienta.
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`.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 GHCR image tag is published, returning a GO / NO-GO verdict per surface. Agent-callable surface of `greenlight shipcheck`.
No se publicó ningún esquema de entrada para esta herramienta.
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`.Contributor 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`.
No se publicó ningún esquema de entrada para esta herramienta.
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 con…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 has been dead since 2025 while thousands of issues still wear its labels)? Returns the classification with its evidence. Context for the con…
No se publicó ningún esquema de entrada para esta herramienta.
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.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-gated repos. DRY RUN BY DEFAULT: returns the comment plan without posting unless execute is true, and posting requires GITHUB_TOKEN.
No se publicó ningún esquema de entrada para esta herramienta.
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 i…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), and write a local PREP.md checklist (verdict, gates, DCO reminders, next commands). Never clones. DRY RUN BY DEFAULT: no fork or branch i…
No se publicó ningún esquema de entrada para esta herramienta.
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 wi…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-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 wi…
No se publicó ningún esquema de entrada para esta herramienta.
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 (de…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 check history, and classifies each failing check as pre-existing, likely-yours, indeterminate (with a stated lean), or external-blocker (de…
No se publicó ningún esquema de entrada para esta herramienta.
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…Triage 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…
No se publicó ningún esquema de entrada para esta herramienta.
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 ma…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 author, missing required artifacts (changeset file, DCO sign-off, CLA status), and whether the author is a first-time contributor. Returns ma…
No se publicó ningún esquema de entrada para esta herramienta.
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…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 arbitration), claimed-by-other conflicts (an open PR whose linked issue was claimed by someone else first), stale claims (issues claimed 14+ days…
No se publicó ningún esquema de entrada para esta herramienta.
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…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 the protocol at all. Returns the SPEC 5.1 status payload with competing PRs and gates merged from the check machinery. The verdict vocabulary…
No se publicó ningún esquema de entrada para esta herramienta.
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…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 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…
No se publicó ningún esquema de entrada para esta herramienta.
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, repro…Draft 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, repro…
No se publicó ningún esquema de entrada para esta herramienta.
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 wh…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, stuck checks), waiting on them (checks running, green with no feedback yet), quiet. Compares against stored watermarks so reruns report only wh…
No se publicó ningún esquema de entrada para esta herramienta.
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 yo…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 document where every claim cites its source (check run, review anchor, claim comment URL). Call this when a maintainer, a recruiter, or yo…
No se publicó ningún esquema de entrada para esta herramienta.
scout_campaignSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
my_claimsSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
sync_campaignSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
campaign_portfolioSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
autopilot_reportSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
api_statusSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
claim_via_apiSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
heartbeat_via_apiSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
ci_prepSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
pr_radarSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
pr_briefSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
21 de 33 herramientas publicaron una descripción.
Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.
Pre-flight and coordination layer for open-source contribution: issue verdicts, Timeline X-Ray, PR radar and review briefs. CLI + MCP server.
Los nombres enlazados abren el índice de Forge con todas las entradas que se observó que exponen esa herramienta. Ver todas las herramientas indexadas.
El rastreo se detuvo en el límite de profundidad 4. Nada por debajo de ese nivel llegó a resolverse.
El rastreo se detuvo en el límite de 60 paquetes. El resto del árbol nunca se resolvió.
Hay 36 paquetes resueltos más que no se dibujan aquí (límite de visualización: 24). Toda dependencia con avisos de seguridad se dibuja aunque se supere el límite. Inventario completo (SBOM CycloneDX)
55 dependencias declaradas nunca llegaron al árbol. Faltan en la resolución de Forge, no en el paquete.
+43 más sin listar. Los recuentos por motivo de arriba las incluyen todas.
No se siguen: peerDependencies. Este árbol cubre solo dependencias en tiempo de ejecución, así que lo que estas arrastren nunca se resolvió.