mcp@0.4.24
VERIFIED· install onlyPublisher claims: "Model Context Protocol (MCP) server for the Lightsage Public API." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
CLERK_SECRET_KEYLIGHTSAGE_API_KEYLIGHTSAGE_API_KEY_AUTHLIGHTSAGE_LIGHTSAGE_API_KEY_AUTHLIGHTSAGE_MCP_TRACKER_API_KEYMCP_EXCHANGE_SECRETMCP_OAUTH_ENABLEDor--lightsage-api-key-authConfiguration, not credentials: CLERK_PUBLISHABLE_KEY, LIGHTSAGE_EXCHANGE_URL, MCP_RESOURCE_URL- Where it talks to
- lightsage.com (its own)Also speakeasy.com, usesapient.com, gstatic.com, cursor.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names speakeasy.com, usesapient.com, gstatic.com, cursor.com as well as its own vendor. The guard injects CLERK_SECRET_KEY, LIGHTSAGE_API_KEY, LIGHTSAGE_API_KEY_AUTH, LIGHTSAGE_LIGHTSAGE_API_KEY_AUTH, LIGHTSAGE_MCP_TRACKER_API_KEY, MCP_EXCHANGE_SECRET, MCP_OAUTH_ENABLED only into requests to lightsage.com (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.4.23
vet-skills diff mcp 0.4.23 0.4.24This version reaches for something 0.4.23 did not: 5 new hosts (cursor.com, gstatic.com, lightsage.com, speakeasy.com, …) · 7 new credential variables (CLERK_SECRET_KEY, LIGHTSAGE_API_KEY, LIGHTSAGE_API_KEY_AUTH, LIGHTSAGE_LIGHTSAGE_API_KEY_AUTH, …). Compared from the two recorded runs, not from source.
- New hosts
- cursor.com, gstatic.com, lightsage.com, speakeasy.com, usesapient.com
- New credential variables
- CLERK_SECRET_KEY, LIGHTSAGE_API_KEY, LIGHTSAGE_API_KEY_AUTH, LIGHTSAGE_LIGHTSAGE_API_KEY_AUTH, LIGHTSAGE_MCP_TRACKER_API_KEY, MCP_EXCHANGE_SECRET, MCP_OAUTH_ENABLED
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-09 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
globals.process?.env ?? globals.Deno?.env?.toObject?.() ?? {},Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary> Stdio installation via npm </summary> To start the MCP server, run: ```bash npx @lightsage/mcp start --lightsage-api-key-auth ``` For a full list of sFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<link href="https://fonts.googleapis.com/css2?family=Geist+Mono:[email protected]&family=Geist:[email protected]&display=swap" rel="stylesheet">Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<code class="code-snippet language-json" id="claude-cli-cmd">claude mcp add LightsageMcp -- npx -y @lightsage/mcp start --lightsage-api-key-auth </code>Fix: Pin versions and sources; vendor anything fetched at install time.<code class="code-snippet language-json" id="gemini-config">gemini mcp add LightsageMcp -- npx -y @lightsage/mcp start --lightsage-api-key-auth </code>Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for @lightsage/mcp@0.4.24 as of 10d ago. This is the package itself, not its dependencies.