MCP servers › io.github.CloudCorpRecords › greenlight

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.CloudCorpRecords/greenlight

Pre-flight checks for open-source contributions: is this GitHub issue actually landable? — the publisher's description

7 of 9 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedversion 0.21.1TypeScriptMITstandard input/output33 tools

Summary

io.github.CloudCorpRecords/greenlight is a local MCP server listed in the official MCP registry at version 0.21.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 33 tools, 0 resources and 0 prompts.

Record checks

7 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#474 of 15,112 packages by monthly downloads
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm, Docker (OCI) · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 33
Described as changing data: 9 of 33 toolsAI-classified
Mainly works on: files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
Topic: developer-toolsAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

9 tools are described as changing something (verify, claim_issue, prep_issue, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.21.1, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-16 (earliest version still in the registry; older removed versions would be earlier)

Version history

40 versions listed, 2026-10-16 to 2026-10-22; 40 in the 90 days before the 2026-10-23 snapshot.

Most recent 12 versions

0.21.1 · 2026-10-22
0.21.0 · 2026-10-21
0.20.1 · 2026-10-21
0.20.0 · 2026-10-21
0.19.0 · 2026-10-20
0.18.0 · 2026-10-20
0.17.1 · 2026-10-20
0.17.0 · 2026-10-20
0.16.2 · 2026-10-20
0.16.1 · 2026-10-19
0.16.0 · 2026-10-19
0.15.1 · 2026-10-19

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.21.1 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

33tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

9 of 33 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

check_issueon 1 other serverreads or searches
“Verdict on whether a GitHub issue is actually landable for an outside contributor.”
1 input, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
scan_repoon 9 other serversreads or searches
“Rank a repo's open issues by verdict, GO first.”
2 inputs, 1 required
- repostringrequired“owner/repo, e.g.”
- deepboolean“Timeline X-Ray the ranked candidates: demotes issues with hidden in-flight PRs (reporter-owned fix PRs, timeline cross-references) before returning.”
xray_issuesreads or searches
“Timeline X-Ray: deep-verify candidate issues against their GitHub timelines before writing code.”
4 inputs, 1 required
- repostringrequired“owner/repo, e.g.”
- issuesstring“Comma-separated issue numbers, e.g.”
- from_scanboolean“X-ray the scan's top candidates instead of listing issue numbers.”
- limitnumber“Max issues to x-ray (default 10).”
racecheck_issuereads or searches
“Keyword 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.”
2 inputs, 2 required
- repostringrequired“owner/repo, e.g.”
- issuenumberrequired“Issue number, e.g.”
repo_frictionreads or searches
“Friction score 0-100 for a repo (100 = easiest to land an outside PR).”
1 input, 1 required
- repostringrequired“owner/repo, e.g.”
wave_queuereads or searches
“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), exclude…”
8 inputs
- index_urlstring“Policy index URL or local file path.”
- max_reposnumber“Candidate repos to process (default 10).”
- min_sharenumber“Minimum outsider merge share 0-100 (default 40).”
- min_starsnumber“Star band floor (default 1000).”
- max_starsnumber“Star band ceiling (default 150000).”
- issues_per_reponumber“Starter issues x-rayed per repo (default 3).”
- min_budgetnumber“Core API floor; the run stops with partial results under it (default 800).”
- sortstring“Candidate ranking: winnability (outsider merge share, then friction, then stars) or stars (default winnability).”
verifyon 60 other serversruns code or commandsdescribed as changing data
“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.”
6 inputs
- dirstring“Repo checkout to verify.”
- basestring“Base ref for the comparison (default: merge-base with upstream, or origin/main).”
- cmdstring“Override the detected test command.”
- parserstring“Override the result parser (e.g.”
- timeout_secsnumber“Per-run timeout in seconds.”
- allow_dirtyboolean“Run even when the working tree has uncommitted changes.”
shipcheckreads or searches
“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…”
4 inputs, 2 required
- repostringrequired“owner/repo of the release.”
- versionstringrequired“Release version without the v prefix, e.g.”
- npm_packagestring“npm package name; defaults from package.json, then the API.”
- mcp_namestring“MCP registry server name; defaults from server.json, then the API.”
passporton 1 other serverreads or searches
“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.”
1 input, 1 required
- loginstringrequired“GitHub login (a leading @ is fine).”
bounty_checkreads or searches
“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…”
1 input, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
claim_issuecreates or changes datadescribed as changing data
“Post a claim comment on a GitHub issue, shaped by the repo's contribution gates.”
5 inputs, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
- executeboolean“Post the comment for real.”
- forceboolean“Claim even on a TAKEN or STALE verdict.”
- planstring“Plan recorded in the protocol claim comment (plan: line).”
- eta_daysnumber“ETA in days recorded in the protocol claim comment (eta-days: line).”
prep_issuecreates or changes datadescribed as changing data
“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 (…”
3 inputs, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
- executeboolean“Actually create the fork/branch.”
- dirstring“Directory for PREP.md.”

Show 21 more tools

open_prcreates or changes datadescribed as changing data
“Open a pull request for an issue from your fork branch.”
4 inputs, 2 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
- branchstringrequired“Fork branch to open the PR from, e.g.”
- executeboolean“Open the PR for real.”
- titlestring“PR title override.”
ci_triagereads or searches
“Answer the red-PR question: is this failure mine or pre-existing?”
1 input, 1 required
- pr_urlstringrequired“Full GitHub PR URL, e.g.”
review_triagereads or searches
“Triage the review feedback on your PR: which comments actually need you?”
1 input, 1 required
- pr_urlstringrequired“Full GitHub PR URL, e.g.”
guard_prreads or searches
“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 (chang…”
1 input, 1 required
- pr_urlstringrequired“Full GitHub PR URL, e.g.”
repo_digeston 1 other serverreads or searches
“Repo-level maintainer report: what needs attention across the whole repo?”
2 inputs, 1 required
- repostringrequired“owner/repo, e.g.”
- limitnumber“Max open PRs and open issues to inspect.”
claim_statuson 4 other serversreads or searches
“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.”
1 input, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
preflighton 16 other serversreads or searches
“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 …”
1 input, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
verify_commentgenerates content
“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 …”
10 inputs, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
- claimstring“One-line claim of the problem.”
- environmentstring“Environment: repo, ref/commit, date, platform.”
- reproductionstring“Reproduction steps, one per line, exact commands.”
- observedstring“What was observed when the repro ran.”
- expectedstring“What should have happened instead.”
- root_causestring“Root cause with file paths and line refs when known; empty renders 'not yet isolated'.”
- fixstring“Proposed fix sketch, not a code dump.”
- ranstring“What was actually run (commands, counts).”
- verified_bystring“Who ran the verification.”
babysit_prsreads or searches
“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 runn…”
5 inputs
- pr_urlsarray“Full GitHub PR URLs to watch, e.g.”
- mineboolean“Discover the author's open PRs across the repos list via the GitHub search API.”
- reposarray“owner/repo list for mine discovery, e.g.”
- authorstring“Author whose open PRs to discover with mine.”
- state_pathstring“Watermark file.”
evidence_packon 4 other serversgenerates content
“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 s…”
2 inputs, 1 required
- pr_urlstringrequired“Full GitHub PR URL, e.g.”
- verify_jsonstring“Path to a prior `greenlight verify --json` report to include the honest red-green test delta.”
scout_campaigncreates or changes datadescribed as changing data
“Campaign 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.”
6 inputs, 2 required
- reposarrayrequired“owner/repo list, e.g.”
- campaign_pathstringrequired“Path to the campaign JSON file ({ entries: [{repo, issue, status, pr}], cursor })”
- budgetnumber“Max GitHub API calls; a resume cursor is saved on budget hit”
- writeboolean“Append survivors to the campaign file; false prints only”
- scan_limitnumber“Issues scanned per repo (default 10)”
- keepnumber“Survivors kept per repo (default 5)”
my_claimsreads or searches
“The 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…”
1 input
- claims_registry_pathstring“Override path for the my-claims registry.”
sync_campaigncreates or changes datadescribed as changing data
“Reconcile 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.”
3 inputs
- authorstring“GitHub login; default GREENLIGHT_GITHUB_USER or CloudCorpRecords”
- writeboolean“Upsert the registry's known-PRs section from the census”
- stale_daysnumber“Claims without a PR older than this are stale”
campaign_portfolioreads or searches
“One-screen campaign summary: census counts (open/merged/closed), claims by state, the pending posting queue, and the sync drift count.”
2 inputs
- authorstring“GitHub login; default GREENLIGHT_GITHUB_USER or CloudCorpRecords”
- stale_daysnumber“Claims without a PR older than this are stale”
autopilot_reportreads or searches
“Autopilot 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-…”
2 inputs
- authorstring“GitHub login; default GREENLIGHT_GITHUB_USER or CloudCorpRecords”
- max_prsnumber“Cap discovered PRs”
api_statuson 4 other serversreads or searches
“The 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.”
2 inputs, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
- api_basestring“Override the hosted claim API base URL.”
claim_via_apicreates or changes datadescribed as changing data
“Claim one issue through the hosted claim API.”
7 inputs, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
- executeboolean“Post the claim for real.”
- planstring“Plan recorded in the protocol claim comment (plan: line).”
- eta_daysnumber“ETA in days recorded in the protocol claim comment (eta-days: line).”
- queue_okboolean“Join the public queue when someone else holds the active claim.”
- api_basestring“Override the hosted claim API base URL.”
- tokenstring“API token passthrough; prefer the stored token from greenlight auth login.”
heartbeat_via_apicreates or changes datadescribed as changing data
“Renew one active claim through the hosted claim API (extends the lease).”
5 inputs, 1 required
- issue_urlstringrequired“Full GitHub issue URL, e.g.”
- executeboolean“Post the heartbeat for real.”
- modestring“Renew with a comment or a reaction, where supported.”
- api_basestring“Override the hosted claim API base URL.”
- tokenstring“API token passthrough; prefer the stored token from greenlight auth login.”
ci_prepruns code or commandsdescribed as changing data
“Run 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…”
4 inputs, 1 required
- pathstringrequired“Local path to the target repo checkout, e.g.”
- basestring“Base git ref for convention checks (default: auto-detect).”
- use_actboolean“Run workflows via act+docker when available; falls back to native mode when not.”
- timeout_secsnumber“Per-step execution timeout in seconds.”
pr_radarreads or searches
“Maintainer-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 budg…”
2 inputs, 1 required
- repostringrequired“owner/repo, e.g.”
- limitnumber“Cap open PRs scanned (default 25, max 100).”
pr_briefreads or searches
“Verified 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 e…”
1 input, 1 required
- targetstringrequired“PR URL or owner/repo#N, e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 33 tools
Says what it returns: 100% of 33 tools
States limits, defaults or errors: 31% of 29 tools
Says when to use it: 100% of 33 tools
Items covered per tool: 3.4 of 4 on average

Counted from the listing

Parameters with a description: 100% of 101
Tools with a description: 100% of 33
Typical description length: 360 characters

The tool set

Counted from the listing

Tools: 33
Size of the list: about 7,608 tokens for an agent to load (characters ÷ 4)
Naming: 29 of 33 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 33 of 33 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @reneturcios/greenlight

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "greenlight": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/greenlight@0.21.1",
        "mcp"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "greenlight": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/greenlight@0.21.1",
        "mcp"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "greenlight": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/greenlight@0.21.1",
        "mcp"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"greenlight","type":"stdio","command":"npx","args":["-y","@reneturcios/greenlight@0.21.1","mcp"]}'

Claude Code

claude mcp add --transport stdio greenlight -- npx -y @reneturcios/greenlight@0.21.1 mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @reneturcios/greenlight@0.21.1 mcp

Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.21.1
Latest stable: 0.21.1
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-2SdEmZF8KnBun5rzG…
Signature: signed
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 4,637 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.21.1 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/CloudCorpRecords/greenlight	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.CloudCorpRecords · 15 servers
GitHub owner: a personal account (CloudCorpRecords)
Build record: signed

Repository: github.com/CloudCorpRecords/greenlight
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 9 record checks met

#474 of 15,112 packages by monthly downloads
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.CloudCorpRecords/greenlight

Answered from the data above

Is io.github.CloudCorpRecords/greenlight safe to install?

We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 9 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.CloudCorpRecords/greenlight been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.CloudCorpRecords/greenlight do?

It lists 33 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, run code or commands and generate content. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.CloudCorpRecords/greenlight change or delete data?

9 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.CloudCorpRecords/greenlight publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.21.1, the latest stable release on npm.

Where is the source code of io.github.CloudCorpRecords/greenlight?

In github.com/CloudCorpRecords/greenlight, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.tomyud1/godot-mcpalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.Keesan12/martin-loopMartin Loopalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.IMNMV/clauderClaudeR - RStudio MCP Serveralso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.SummerEngine/summerSummer Enginealso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.SupportPages-io/wtfmWTFMalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.mybolide/mcp-probe-kitalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
2,937 msConnected after 0 redirects.
Read the inventory: 33 tools, 0 resources, 0 prompts.
4,071 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm, oci

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

4,637 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.CloudCorpRecords/greenlight: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.CloudCorpRecords/greenlight

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.CloudCorpRecords/greenlight)](https://protocolprobe.com/mcp/servers/io.github.CloudCorpRecords/greenlight)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology