Lumaion Continuity
REMOTE · MCP.LUMAION.APP
Agent continuity: live continuity index, self-test contract, offline Continuity Proof verification.
Available components
Last scanned (23 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Memory and Knowledge
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 308 tokens (~102/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +10
- Transport: fail → pass ▲ security
- 21 Oct 26 −9
- Transport: pass → fail ▼ security
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 4 Nov 2026 · Probed https://mcp.lumaion.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.lumaion.app | CN=YR2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | RSA 2048 | SHA256-RSA | 6ee7fb355daf7762c5990fec59d1c214c08 |
| SANs: *.lumaion.app, lumaion.app | ||||||
| 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 mcp.lumaion.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| lumaion.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lumaion.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.lumaion.app/mcp | HTTPS enforced | 308 | https://mcp.lumaion.app/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 →
get_continuity_index Agent Continuity Index ~81
Returns the live, read-only Agent Continuity Index: how many public MCP servers mention memory, how many build memory infrastructure, and A2A Agent Card adoption among probed hosts, with a daily trend. Aggregates only; no agent is named or ranked.
| Name | Type | Req | Description |
|---|---|---|---|
| include_trend | boolean | – | Include the daily trend series (default false). |
No output schema declared.
No examples provided.
get_continuity_test_contract Continuity self-test contract ~78
Describes the voluntary Lumaion continuity self-test an agent operator can run: Ed25519 identity, checkpoint a small synthetic state, discard the runtime, restore in a new runtime, receive a server-signed Continuity Proof verifiable offline. Returns the live contract and the one-file reference client. Does not start a test.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_continuity_proof Verify a Continuity Proof ~108
Verifies a Lumaion Continuity Proof offline against the published proof keys: payload hash, server Ed25519 signature, both runtime delegations signed by the agent identity key, and that the runtime changed. Pass either a full proof JSON object or the proof_id of a PUBLISHED proof.
| Name | Type | Req | Description |
|---|---|---|---|
| proof | object | – | Full Continuity Proof JSON (lumaion continuity proof v1). |
| proof_id | string | – | ID of a published proof to fetch and verify. |
No output schema declared.
No examples provided.
How do I install the Lumaion Continuity MCP server?
Lumaion Continuity is a hosted endpoint at https://mcp.lumaion.app/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 · mcp.lumaion.app
claude mcp add --transport http app-lumaion-continuity 'https://mcp.lumaion.app/mcp'
What is the Lumaion Continuity MCP server?
Lumaion Continuity is an MCP server listed in the public MCP registry as app.lumaion/continuity. Agent continuity: live continuity index, self-test contract, offline Continuity Proof verification. This page covers its hosted endpoint (https://mcp.lumaion.app/mcp).
Is the Lumaion Continuity MCP server safe to use?
Lumaion Continuity scores 89 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 Lumaion Continuity MCP server expose?
Lumaion Continuity exposes 3 tools: get_continuity_index, get_continuity_test_contract, verify_continuity_proof. Their descriptions and schemas cost roughly 267 tokens of context every time the server is loaded.
Does the Lumaion Continuity MCP server require authentication?
No. We connected to Lumaion Continuity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lumaion Continuity MCP server still maintained?
Lumaion Continuity is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.