# LightSpot (npm · @lightspot/mcp)

Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes.

- Trust score: 84/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@lightspot/mcp`: 84/100 (this document), [markdown](https://verifymcp.io/servers/nmarijane-lightspot-mcp/lightspot-mcp.md), [page](https://verifymcp.io/servers/nmarijane-lightspot-mcp/lightspot-mcp)

## Channel facts

- Registry: `npm`
- Package: `@lightspot/mcp`
- Version: `0.6.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 31 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 937 tokens (~85/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add nmarijane-lightspot-mcp -- npx -y @lightspot/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "nmarijane-lightspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@lightspot/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nmarijane-lightspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@lightspot/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nmarijane-lightspot-mcp -- npx -y @lightspot/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nmarijane-lightspot-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@lightspot/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nmarijane-lightspot-mcp --command npx --arg -y --arg @lightspot/mcp
```

### Hermes

```yaml
mcp_servers:
  nmarijane-lightspot-mcp:
    command: "npx"
    args: ["-y", "@lightspot/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "nmarijane-lightspot-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@lightspot/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add nmarijane-lightspot-mcp -t stdio -c npx -a -y @lightspot/mcp
```

### Other

```json
{
  "mcpServers": {
    "nmarijane-lightspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@lightspot/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 84, +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.

### 2026-10-29 (score 83, +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.

### 2026-10-27 (score 82, +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.

### 2026-10-25 (score 81, +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.

### 2026-10-23 (score 80, +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.

### 2026-10-21 (score 79, +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.

### 2026-10-18 (score 78, +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.

## MCP tools (11)

### `audit_and_wait` (~124 tokens)

Audit a URL and wait for the result

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.

Input parameters:

- `maxPages` (integer): Number of pages to crawl (capped by your plan).
- `url` (string, required): URL to audit (home page or a specific page).

### `run_audit` (~85 tokens)

Start an audit (non-blocking)

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.

Input parameters:

- `maxPages` (integer): Number of pages to crawl.
- `siteId` (string): Attach the audit to an existing site (optional).
- `url` (string, required): URL to audit.

### `get_audit_status` (~46 tokens)

Get audit status

Lightweight status of an audit (PENDING/RUNNING/DONE/FAILED) with a progress value from 0 to 1.

Input parameters:

- `id` (string, required): Audit identifier.

### `get_audit` (~69 tokens)

Get audit results

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).

Input parameters:

- `full` (boolean): true for the full payload, otherwise a summary.
- `id` (string, required): Audit identifier.

### `list_sites` (~45 tokens)

List your sites

Paginated list of your LightSpot team's sites (with their latest score).

Input parameters:

- `limit` (integer): Page size (default 50).
- `offset` (integer): Pagination offset.

### `get_site` (~25 tokens)

Get a site

A site's metadata and its recent audits.

Input parameters:

- `id` (string, required): Site identifier.

### `list_site_audits` (~50 tokens)

List a site's audit history

Paginated audit history of a site.

Input parameters:

- `id` (string, required): Site identifier.
- `limit` (integer): Page size (default 50).
- `offset` (integer): Pagination offset.

### `get_competitors` (~67 tokens)

Get a site's competitor analysis

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".

Input parameters:

- `siteId` (string, required): Site identifier.

### `get_expert_report` (~238 tokens)

Get a site's expert report

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.

Input parameters:

- `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, required): LightSpot site identifier.

### `get_editorial_calendar` (~94 tokens)

Read a site's editorial calendar

Reads a site's LightSpot editorial calendar over a period: imported slots, content being prepared, scheduled or published, and upcoming autopilot runs.

Input parameters:

- `from` (string, required): Inclusive start of the period, ISO 8601 with time zone.
- `siteId` (string, required): LightSpot site identifier.
- `to` (string, required): Exclusive end of the period, ISO 8601 with time zone (366 days maximum).

### `create_editorial_calendar` (~94 tokens)

Create or update an editorial calendar

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.

Input parameters:

- `items` (array, required): Slots to show in the LightSpot calendar.
- `siteId` (string, required): LightSpot site identifier.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nmarijane-lightspot-mcp/lightspot-mcp#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-11: 74
- 2026-10-04: 71
- 2026-10-03: 56
- 2026-10-02: 55

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@lightspot/mcp
- Socket report: https://socket.dev/npm/package/@lightspot/mcp
- Repository: https://github.com/nmarijane/lightspot-mcp
- Website: https://lightspot.ai/
- Changelog RSS feed: https://verifymcp.io/servers/nmarijane-lightspot-mcp/lightspot-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nmarijane-lightspot-mcp/lightspot-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nmarijane-lightspot-mcp/lightspot-mcp.json
- HTML version of this page: https://verifymcp.io/servers/nmarijane-lightspot-mcp/lightspot-mcp