# Moatlight (remote · moatlight.com)

Measure AI search visibility: start reports, read results and the ranked plan.

- Trust score: 33/100 (low)
- Change this week: −37
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `moatlight.com`: 33/100 (this document), [markdown](https://verifymcp.io/servers/com-moatlight-mcp/moatlight.md), [page](https://verifymcp.io/servers/com-moatlight-mcp/moatlight)

## Channel facts

- Endpoint: `https://moatlight.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Moatlight MCP server?

Moatlight is a hosted endpoint at https://moatlight.com/mcp, so there is nothing to install locally. 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 --transport http com-moatlight-mcp 'https://moatlight.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-moatlight-mcp": {
      "url": "https://moatlight.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-moatlight-mcp": {
      "type": "http",
      "url": "https://moatlight.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-moatlight-mcp]
url = "https://moatlight.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-moatlight-mcp": {
      "type": "remote",
      "url": "https://moatlight.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-moatlight-mcp --url 'https://moatlight.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-moatlight-mcp:
    url: "https://moatlight.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-moatlight-mcp": {
      "Transport": "http",
      "Url": "https://moatlight.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-moatlight-mcp -t streamable-http -u 'https://moatlight.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-moatlight-mcp": {
      "type": "http",
      "url": "https://moatlight.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-16 (score 33, −38)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.27 → unverified
- [security regression] Transport: pass → unverified
- [security regression] HSTS header: pass → fail
- [security] Authorization: The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-15 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 68, 0)

- [security] Tool “start_report” rewrote its description, which is the text the model reads

### 2026-11-09 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 67, 0)

- [security] Tool “create_report” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 67)

First indexed and scored.

## MCP tools (13)

### `get_product` (~79 tokens)

What Moatlight does and when to use it

Facts about the product: what it does, who it is for, what it does not do, and how an agent can use it. No login. No login needed.

Input parameters:

- `fields` (string): Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

### `get_pricing` (~80 tokens)

Plans and prices

The free plan and the one-time Early Access pass: price, what each includes, refund window. Payment needs a person in a browser. No login. No login needed.

Input parameters:

- `fields` (string): Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

### `list_faq` (~75 tokens)

Frequently asked questions

Every FAQ question and answer from the home page, paged. No login. No login needed.

Input parameters:

- `cursor` (string): Opaque cursor: send next_cursor from the previous page unchanged. Omit for the first page.
- `limit` (integer): Items per page, 1 to 50. Default 20.

### `get_sample_report` (~79 tokens)

A finished sample report on made-up data

Shows the shape of a real report (visibility numbers, rivals, ranked plan) for a fictional coffee roaster. Made-up data, no login. No login needed.

Input parameters:

- `fields` (string): Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

### `get_account` (~77 tokens)

The signed-in user, plan and limits

Returns the user's plan (free or early_access), when the pass ends, what the plan allows, and how to upgrade. Needs login with scope account:read.

Input parameters:

- `fields` (string): Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

### `list_reports` (~93 tokens)

List the user's reports

The user's reports, newest first, paged with a cursor. Each has its stage (analyzing, needs_confirmation, running, finished, failed). Needs login with scope reports:read.

Input parameters:

- `cursor` (string): Opaque cursor: send next_cursor from the previous page unchanged. Omit for the first page.
- `limit` (integer): Items per page, 1 to 50. Default 20.

### `create_report` (~182 tokens)

Start a report for a website

Creates a report draft for a website and starts reading it. Free plan: one website, one report every 30 days. A new draft for a different website deletes the user's unfinished draft for the old one, so ask the user first. Returns 202 Accepted with the report, a job object and a Location header: poll that URL (GET /api/v1/reports/{reportId}) every few seconds until stage is needs_confirmation, then call the start endpoint. Send an Idempotency-Key header so a retry cannot start a second report. Needs login with scope reports:write.

Input parameters:

- `country` (string): Optional two-letter country. Send with language, or omit both to detect from the site.
- `language` (string): Optional language for that country.
- `website` (string, required): The website to measure, like yourcompany.com. Public sites only.

### `batch_get_reports` (~84 tokens)

Read up to 25 reports in one request

Batch read: send a list of report ids and get each report (or its error) in one answer, instead of one call per report. Each result has its own status, so one unknown id does not fail the rest. Read-only. Needs login with scope reports:read.

Input parameters:

- `report_ids` (array, required): Report ids to read, 1 to 25.

### `get_report` (~119 tokens)

Read one report: stage, setup to confirm, or results

While stage is needs_confirmation it returns the business profile and the proposed buyer questions. While running it returns progress. When finished it returns visibility numbers, the brands AI named, and a count of lost questions. Needs login with scope reports:read.

Input parameters:

- `fields` (string): Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.
- `reportId` (string, required): Report id from POST /api/v1/reports or GET /api/v1/reports.

### `start_report` (~158 tokens)

Confirm the setup and run the report

Accepts the proposed business profile and buyer questions (optionally a chosen subset of 3 to 6 question ids) and starts asking the AI engines the account includes (listed in limits.engines on GET /api/v1/me). Takes about 2 minutes: answers 202 Accepted with a Location header to poll until stage is finished. Safe to repeat; send an Idempotency-Key header to make a retry return the first answer. Needs login with scope reports:write.

Input parameters:

- `question_ids` (array): Ids of the 3 to 6 questions to ask. Omit to keep the proposed selection.
- `reportId` (string, required): Report id from POST /api/v1/reports or GET /api/v1/reports.

### `get_report_actions` (~116 tokens)

The ranked plan of changes and the questions you lost

For a finished report: up to three ranked moves (reason, exact edit, page, effort) and, for each buyer question AI answered with a rival, who won and why. Needs login with scope reports:read.

Input parameters:

- `fields` (string): Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.
- `reportId` (string, required): Report id from POST /api/v1/reports or GET /api/v1/reports.

### `get_agent_readiness` (~121 tokens)

Stored agent readiness scan (Early Access pass)

Score, grade, layer breakdown and ranked fixes from the newest scan of the report's website. Needs the Early Access pass; otherwise 402 with a link a person can open to buy it. Needs login with scope agent-readiness:read.

Input parameters:

- `fields` (string): Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.
- `reportId` (string, required): Report id from POST /api/v1/reports or GET /api/v1/reports.

### `scan_agent_readiness` (~94 tokens)

Run an agent readiness scan (Early Access pass)

Runs, or reuses a result under 24 hours old, for the report's website. Set force to true to scan again after fixing something. Rate limited. Needs login with scope agent-readiness:scan.

Input parameters:

- `force` (boolean): Scan again even if a recent result exists.
- `reportId` (string, required): Report id from POST /api/v1/reports or GET /api/v1/reports.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-moatlight-mcp/moatlight#diagnostics

## Score history

- 2026-11-21: 33
- 2026-11-20: 33
- 2026-11-19: 33
- 2026-11-18: 33
- 2026-11-17: 33
- 2026-11-16: 33
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 69
- 2026-11-10: 68
- 2026-11-09: 68
- 2026-11-08: 67
- 2026-11-07: 67

## Common questions

### What is the Moatlight MCP server?

Moatlight is an MCP server listed in the public MCP registry as com.moatlight/mcp. Measure AI search visibility: start reports, read results and the ranked plan. This page covers its hosted endpoint (https://moatlight.com/mcp).

### Is the Moatlight MCP server safe to use?

Moatlight scores 33 out of 100 on VerifyMCP. 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 Moatlight MCP server expose?

Moatlight exposes 13 tools: get_product, get_pricing, list_faq, get_sample_report, get_account, and 8 more. Their descriptions and schemas cost roughly 1,357 tokens of context every time the server is loaded.

### Does the Moatlight MCP server require authentication?

Yes. Moatlight asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Moatlight MCP server still maintained?

Moatlight 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 did VerifyMCP test on the Moatlight MCP server?

VerifyMCP ran 5 checks on Moatlight, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Moatlight: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://moatlight.com/mcp
- Repository: https://github.com/Moatlight/moatlight-agent-kit
- Website: https://moatlight.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-moatlight-mcp/moatlight.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-moatlight-mcp/moatlight/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-moatlight-mcp/moatlight.json
- HTML version of this page: https://verifymcp.io/servers/com-moatlight-mcp/moatlight
