Greenlit
NPM · GREENLITLAB
Grade apps built with Lovable, Bolt, v0 or Replit A to F, with a fix prompt for every problem.
Available components
Last scanned (21 hours ago)
Scores higher than 56% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 618 tokens (~154/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Schema quality: 211 → 154 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- Package version: 0.2.0 → 0.4.2 functional
- 9 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Nov 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/greenlitlab@0.4.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
greenlit_advisor ~117
Turn Supabase's Security or Performance Advisor results into plain-English findings with a fix prompt for each, worst first. Get the results from the Supabase MCP server's get_advisors tool (type "security") for the user's project, then pass them here as `lints`. This is the reliable way to learn which rules are too loose and whether strangers can change or delete data, which no outside check can see.
| Name | Type | Req | Description |
|---|---|---|---|
| lints | – | yes | The advisor output: a list of lints, or the object that contains one. |
No output schema declared.
No examples provided.
greenlit_check ~244
Grade a deployed web app (built with Lovable, Bolt, v0, Replit, Emergent or by hand) A to F for what a stranger can use against it: secret keys shipped in its JavaScript (Stripe, OpenAI, OpenRouter, Supabase secret keys and 28 more kinds), a Supabase service_role key in the browser, source maps, clickjacking and missing security headers, plus launch basics (developer-only addresses, Stripe test mode, a test email sender, no https redirect, open CORS, missing DMARC on a custom domain). Every finding has a plain-English reason and a fix prompt; `allFixes` has every fix in one prompt, worst first. Reads only what the site serves to every visitor. Call it again after a fix: `change` shows what got fixed. For the user's own app, have them run `npx greenlitlab <url> --mine`: it also checks which database tables and storage buckets anyone can read, open sign-up, and public .env or .git files.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The app's address, for example myapp.lovable.app |
No output schema declared.
No examples provided.
greenlit_questions ~121
Seven launch questions only the app's owner can answer (backups and restore, separate test database, hard spending limits, payment webhook checks, outage alerts, email sender, database plan). Call with no arguments to get the questions and options to ask the user. Call with `answers` ({questionId: optionKey}) to get, for each gap, the fact that makes it matter and a fix prompt. Answers are the owner's word, never graded.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | For example {"backup": "no", "spend": "alerts"} |
No output schema declared.
No examples provided.
greenlit_scan ~136
Read a project folder on this computer for launch mistakes that can't be seen from outside, before deploying: Row Level Security policies whose condition is just `true`, tables created without RLS, Supabase edge functions with verify_jwt = false, Stripe webhook handlers that never verify the signature, secrets behind a public prefix (VITE_, NEXT_PUBLIC_), a tracked .env file, and an agent config with a writable database connection. Pattern-based, not a full code review. Reads names in .env files, never values. Each finding has a fix prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The project folder. Defaults to the current folder. |
No output schema declared.
No examples provided.
How do I install the Greenlit MCP server?
Greenlit runs locally as an npm package, launched with npx -y greenlitlab mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · greenlitlab
claude mcp add priberry-data-greenlitlab -- npx -y greenlitlab mcp
What is the Greenlit MCP server?
Greenlit is an MCP server listed in the public MCP registry as io.github.priberry-data/greenlitlab. Grade apps built with Lovable, Bolt, v0 or Replit A to F, with a fix prompt for every problem. This page covers its npm package (greenlitlab).
Is the Greenlit MCP server safe to use?
Greenlit scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Greenlit MCP server expose?
Greenlit exposes 4 tools: greenlit_check, greenlit_scan, greenlit_advisor, greenlit_questions. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.
Is the Greenlit MCP server still maintained?
Greenlit is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Greenlit MCP server under?
Greenlit declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Greenlit MCP server?
VerifyMCP ran 16 checks on Greenlit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.