lucid.page
REMOTE · LUCID.PAGE
Publish Markdown from any agent: POST Markdown, get a gorgeous shareable URL.
Available components
Last scanned (2 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_doc). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 950 tokens (~118/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 29 Oct 26 +2
- Stability: fail → pass ▲ security
- 29 Sept 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “create_bundle” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_docs” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “add_to_binder” functional
- New tool “create_binder” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 11 Sept 26 0
- Tool “update_doc” rewrote its description, which is the text the model reads security
- “update_doc” added an optional parameter “expected_version” cosmetic
- 28 Aug 26 0
- HTTPS: unverified → pass ▲ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://lucid.page/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lucid.page | CN=WE1,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 930f43b5d15b35a4139cfd3b836db8ea |
| SANs: lucid.page, *.lucid.page | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lucid.page. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| page. | present | 64712 | 8 | Verified |
| lucid.page. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lucid.page/mcp | Verified | 200 | |
| http (plaintext) | http://lucid.page/mcp | HTTPS enforced | 301 | https://lucid.page/mcp |
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 →
add_to_binder Add a page or link to a binder ~143
Append one item to a binder you own (requires an lp_ API key). Pass exactly one of slug (a lucid.page page) or url (any http(s) link), plus an optional title (links only) and note.
| Name | Type | Req | Description |
|---|---|---|---|
| binder | string | yes | The binder slug. |
| note | string | – | Optional note shown with the item. |
| slug | string | – | A lucid.page page slug: one of your own pages, or anyone's public or unlisted page. |
| title | string | – | Optional display title for a link. |
| url | string | – | An http(s) link. Links to lucid.page pages are stored as those pages. |
| Name | Type | Req | Description |
|---|---|---|---|
| binder | string | yes | The binder slug |
| item_count | integer | yes | – |
| item_id | string | yes | Id of the added item |
| url | string | yes | The binder page URL |
No examples provided.
create_binder Create a binder ~143
Create a binder: an ordered list of lucid.page pages and external links, each with an optional note, served at https://lucid.page/b/<slug> (requires an lp_ API key). Up to 100 binders per account and 500 items per binder. Public binders with at least one visible item are indexable.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional plain-text description; blank lines start a new paragraph. |
| items | array | – | Optional initial items, in order. Each needs exactly one of slug or url. |
| title | string | yes | The binder title (1-120 characters). |
| visibility | string | – | Defaults to unlisted. |
| Name | Type | Req | Description |
|---|---|---|---|
| item_count | integer | yes | – |
| slug | string | yes | – |
| url | string | yes | The binder page URL, https://lucid.page/b/<slug> |
| visibility | string | yes | – |
No examples provided.
delete_doc Delete a document ~58
Permanently delete a page you own (requires an lp_ API key). The URL stops serving immediately and cannot be recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The document slug — the path part of its https://lucid.page/<slug> URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | string | yes | Slug of the deleted page |
No examples provided.
get_doc Read a document's Markdown ~62
Fetch the canonical Markdown source of a page. Public and unlisted pages are open to anyone; private pages require the owner's lp_ API key.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The document slug — the path part of its https://lucid.page/<slug> URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The canonical Markdown source of the page |
| slug | string | yes | – |
| version | integer | – | Current version; pass as expected_version to update_doc |
No examples provided.
get_limits Get limits and plan status ~37
Show the lucid.page account matrix (anonymous vs lp_ API key) and, when a key is present, the caller's current plan status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | – | Present when an lp_ API key was supplied |
| plans | object | yes | Account matrix: anonymous, with_api_key, pro_team |
No examples provided.
list_docs List your documents ~65
List the documents owned by the authenticated account (requires an lp_ API key), newest first, with cursor pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The nextCursor value from a previous call. |
| limit | integer | – | Max documents to return (1-200, default 50). |
| Name | Type | Req | Description |
|---|---|---|---|
| docs | array | yes | – |
| nextCursor | string|null | yes | Pass as the cursor argument for the next page; null when the listing is exhausted |
No examples provided.
publish_doc Publish a Markdown document ~173
Publish Markdown as a beautifully typeset page and receive its https://lucid.page/<slug> URL. Works anonymously; with an lp_ API key the page is owned by the account and can be updated later. Anonymous publishes return a one-time claim_token — hand your human the claim link https://lucid.page/claim?slug=<slug>&token=<claim_token> so they can claim the page into their account (agents: POST /api/docs/<slug>/claim).
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The Markdown source to publish (max 1 MB). |
| title | string | – | Optional display title. |
| ttl | integer | – | Lifetime in seconds (min 60). Omit for a page that never expires. |
| visibility | string | – | Defaults to unlisted. Private requires an lp_ API key. |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | – | One-time ownership token (anonymous publishes only). A human claims the page at https://lucid.page/claim?slug=<slug>&token=<claim_token>; agents claim with POST /api/docs/<slug>/claim. |
| expires_at | string|null | yes | ISO timestamp, or null when the page never expires |
| slug | string | yes | – |
| url | string | yes | The live page URL. |
| visibility | string | yes | – |
No examples provided.
update_doc Update a published document ~147
Replace the Markdown of a page you own (requires an lp_ API key). The URL stays the same; every update is kept as a revision. Pass expected_version (from get_doc) to guard against overwriting someone else's changes — a conflict returns 409 with current_version.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_version | integer | – | Optional optimistic-lock guard: the version you last read. Saves only if it still matches. |
| markdown | string | yes | The new Markdown source (max 1 MB). |
| slug | string | yes | The document slug — the path part of its https://lucid.page/<slug> URL. |
| title | string | – | Optional new title; omit to keep the current one. |
| Name | Type | Req | Description |
|---|---|---|---|
| revision_hash | string | yes | Content hash of the new revision |
| slug | string | yes | – |
| url | string | yes | – |
| version | integer | – | Monotonic save counter; pass as expected_version next time |
| visibility | string | yes | – |
No examples provided.
How do I install the lucid.page MCP server?
lucid.page is a hosted endpoint at https://lucid.page/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 · lucid.page
claude mcp add --transport http page-lucid-lucid-page 'https://lucid.page/mcp'
What is the lucid.page MCP server?
lucid.page is an MCP server listed in the public MCP registry as page.lucid/lucid-page. Publish Markdown from any agent: POST Markdown, get a gorgeous shareable URL. This page covers its hosted endpoint (https://lucid.page/mcp).
Is the lucid.page MCP server safe to use?
lucid.page scores 79 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 lucid.page MCP server expose?
lucid.page exposes 8 tools: publish_doc, update_doc, get_doc, list_docs, delete_doc, and 3 more. Their descriptions and schemas cost roughly 828 tokens of context every time the server is loaded.
Does the lucid.page MCP server require authentication?
No. We connected to lucid.page without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the lucid.page MCP server still maintained?
lucid.page 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.