Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Moatlight

REMOTE · MOATLIGHT.COM

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

Available components

−37 this week 33 Trust /100

Last scanned (22 hours ago)

Scores higher than 16% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

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. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 16 Nov 26 −38
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.27 → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • 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. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 10 Nov 26 0
    • Tool “start_report” rewrote its description, which is the text the model reads security
  • 9 Nov 26 +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.

  • 8 Nov 26 0
    • Tool “create_report” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 67

    First indexed and scored.

Diagnostics

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 · Probed https://moatlight.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=moatlight.com CN=YR2,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 RSA 2048 SHA256-RSA 64775a5b333d2c3c7c18fe47a25ab2f93e3
SANs: moatlight.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of moatlight.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
moatlight.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 403

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://moatlight.com/mcp Auth required 403
http (plaintext) http://moatlight.com/mcp HTTPS enforced 308 https://moatlight.com/mcp
MCP tools · 13 exposed · ~1,357 tokens

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 →

Tool Tokens
batch_get_reports ~84

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.

NameTypeReqDescription
report_idsarrayyesReport ids to read, 1 to 25.

No output schema declared.

No examples provided.

create_report ~182

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.

NameTypeReqDescription
countrystring–Optional two-letter country. Send with language, or omit both to detect from the site.
languagestring–Optional language for that country.
websitestringyesThe website to measure, like yourcompany.com. Public sites only.

No output schema declared.

No examples provided.

get_account ~77

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.

NameTypeReqDescription
fieldsstring–Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

No output schema declared.

No examples provided.

get_agent_readiness ~121

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.

NameTypeReqDescription
fieldsstring–Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.
reportIdstringyesReport id from POST /api/v1/reports or GET /api/v1/reports.

No output schema declared.

No examples provided.

get_pricing ~80

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.

NameTypeReqDescription
fieldsstring–Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

No output schema declared.

No examples provided.

get_product ~79

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.

NameTypeReqDescription
fieldsstring–Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

No output schema declared.

No examples provided.

get_report ~119

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.

NameTypeReqDescription
fieldsstring–Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.
reportIdstringyesReport id from POST /api/v1/reports or GET /api/v1/reports.

No output schema declared.

No examples provided.

get_report_actions ~116

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.

NameTypeReqDescription
fieldsstring–Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.
reportIdstringyesReport id from POST /api/v1/reports or GET /api/v1/reports.

No output schema declared.

No examples provided.

get_sample_report ~79

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.

NameTypeReqDescription
fieldsstring–Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.

No output schema declared.

No examples provided.

list_faq ~75

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

NameTypeReqDescription
cursorstring–Opaque cursor: send next_cursor from the previous page unchanged. Omit for the first page.
limitinteger–Items per page, 1 to 50. Default 20.

No output schema declared.

No examples provided.

list_reports ~93

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.

NameTypeReqDescription
cursorstring–Opaque cursor: send next_cursor from the previous page unchanged. Omit for the first page.
limitinteger–Items per page, 1 to 50. Default 20.

No output schema declared.

No examples provided.

scan_agent_readiness ~94

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.

NameTypeReqDescription
forceboolean–Scan again even if a recent result exists.
reportIdstringyesReport id from POST /api/v1/reports or GET /api/v1/reports.

No output schema declared.

No examples provided.

start_report ~158

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.

NameTypeReqDescription
question_idsarray–Ids of the 3 to 6 questions to ask. Omit to keep the proposed selection.
reportIdstringyesReport id from POST /api/v1/reports or GET /api/v1/reports.

No output schema declared.

No examples provided.

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.

remote · moatlight.com

# add to Claude Code
claude mcp add --transport http com-moatlight-mcp 'https://moatlight.com/mcp'
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.