LightSpot
NPM · @LIGHTSPOT/MCP
Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes.
Available components
Last scanned (12 hours ago)
Scores higher than 81% of npm servers
Category Marketing and SEO
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 937 tokens (~85/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/@lightspot/mcp@0.6.0
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
audit_and_wait Audit a URL and wait for the result ~124
Runs a LightSpot SEO and AI-visibility audit on a URL, waits for it to finish, and returns a summary (score, top actions, main issues). Ideal for "audit this site and tell me what to fix". Can take 1 to 3 minutes; past the time limit, it returns the id so you can follow up with get_audit_status / get_audit.
| Name | Type | Req | Description |
|---|---|---|---|
| maxPages | integer | – | Number of pages to crawl (capped by your plan). |
| url | string | yes | URL to audit (home page or a specific page). |
No output schema declared.
No examples provided.
create_editorial_calendar Create or update an editorial calendar ~94
Imports up to 50 dated editorial slots into a LightSpot site's calendar. The import is idempotent: externalId lets you update a slot without creating a duplicate. This action only creates the schedule; it does not generate, schedule or publish any content and consumes no AI credit.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Slots to show in the LightSpot calendar. |
| siteId | string | yes | LightSpot site identifier. |
No output schema declared.
No examples provided.
get_audit Get audit results ~69
Fetches the results of an audit: a summary by default (score, top actions, main issues), or the full payload with full=true (all pages and all issues).
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | true for the full payload, otherwise a summary. |
| id | string | yes | Audit identifier. |
No output schema declared.
No examples provided.
get_audit_status Get audit status ~46
Lightweight status of an audit (PENDING/RUNNING/DONE/FAILED) with a progress value from 0 to 1.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Audit identifier. |
No output schema declared.
No examples provided.
get_competitors Get a site's competitor analysis ~67
Fetches a site's latest existing competitor analysis (detected competitors, tiers, citations, recommendations). Requires the Zenith plan. Does NOT trigger a new analysis — if none has been started from the app yet, returns status: "NONE".
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | yes | Site identifier. |
No output schema declared.
No examples provided.
get_editorial_calendar Read a site's editorial calendar ~94
Reads a site's LightSpot editorial calendar over a period: imported slots, content being prepared, scheduled or published, and upcoming autopilot runs.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Inclusive start of the period, ISO 8601 with time zone. |
| siteId | string | yes | LightSpot site identifier. |
| to | string | yes | Exclusive end of the period, ISO 8601 with time zone (366 days maximum). |
No output schema declared.
No examples provided.
get_expert_report Get a site's expert report ~238
Fetches the latest report from our 8 experts (technical SEO, editorial quality, AI visibility, structured data, sitemaps, performance, visual analysis, brand authority) produced after a site audit: prioritized findings, recommended actions with their steps, limitations and ready-to-apply artifacts (JSON-LD, sitemap…). Summary by default (findings + actions); full=true adds the rationale of the actions, the limitations, the artifacts and the evidence; expert=… limits the read to a single expert (useful with full=true to read one whole chapter without loading everything). auditId targets the analysis of a specific audit, otherwise the site's most recent one. Does NOT trigger an analysis — if none exists, returns status: "NONE"; PENDING/RUNNING = try again later.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | – | Identifier of a specific audit (otherwise the site's latest analysis). |
| expert | string | – | Return only this expert's chapter. |
| full | boolean | – | true for the full report (rationale, limitations, artifacts, evidence), otherwise a summary. |
| siteId | string | yes | LightSpot site identifier. |
No output schema declared.
No examples provided.
get_site Get a site ~25
A site's metadata and its recent audits.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Site identifier. |
No output schema declared.
No examples provided.
list_site_audits List a site's audit history ~50
Paginated audit history of a site.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Site identifier. |
| limit | integer | – | Page size (default 50). |
| offset | integer | – | Pagination offset. |
No output schema declared.
No examples provided.
list_sites List your sites ~45
Paginated list of your LightSpot team's sites (with their latest score).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size (default 50). |
| offset | integer | – | Pagination offset. |
No output schema declared.
No examples provided.
run_audit Start an audit (non-blocking) ~85
Starts an SEO and AI-visibility audit on a URL without waiting. Returns the id and status. Use get_audit_status to follow progress and get_audit for the results.
| Name | Type | Req | Description |
|---|---|---|---|
| maxPages | integer | – | Number of pages to crawl. |
| siteId | string | – | Attach the audit to an existing site (optional). |
| url | string | yes | URL to audit. |
No output schema declared.
No examples provided.
How do I install the LightSpot MCP server?
LightSpot runs locally as an npm package, launched with npx -y @lightspot/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 · @lightspot/mcp
claude mcp add nmarijane-lightspot-mcp -- npx -y @lightspot/mcp
What is the LightSpot MCP server?
LightSpot is an MCP server listed in the public MCP registry as io.github.nmarijane/lightspot-mcp. Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes. This page covers its npm package (@lightspot/mcp).
Is the LightSpot MCP server safe to use?
LightSpot scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 LightSpot MCP server expose?
LightSpot exposes 11 tools: audit_and_wait, run_audit, get_audit_status, get_audit, list_sites, and 6 more. Their descriptions and schemas cost roughly 937 tokens of context every time the server is loaded.
Is the LightSpot MCP server still maintained?
LightSpot is still listed as active in the MCP registry. We last reached this channel on 5 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 LightSpot MCP server under?
LightSpot declares the MIT 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 LightSpot MCP server?
VerifyMCP ran 16 checks on LightSpot, 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.