Lumaion Continuity MCP server
app.lumaion/continuitylumaion.appstreamable-httpv0.6.0Scanned
Agent continuity: live continuity index, self-test contract, offline Continuity Proof verification.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Lumaion Continuity MCP server can do
The Lumaion Continuity MCP server is published by lumaion.app, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: verify_continuity_proof), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (get_continuity_index, get_continuity_test_contract and verify_continuity_proof).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 0.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
verify_continuity_proofVerifies 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…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
Only reads 2Show 2 read-only tools
get_continuity_indexReturns 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…Reads text others writeNo findings
Why it is in this group
- The name "get_continuity_index" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "return" and "mention": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
get_continuity_test_contractDescribes 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,…Reads text others writeNo findings
Why it is in this group
- The name "get_continuity_test_contract" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.lumaion.app/mcp: tools/list returned 3 tools to an anonymous client, including verify_continuity_proof (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http continuity https://mcp.lumaion.app/mcpclaude mcp add --transport http continuity https://mcp.lumaion.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__continuity__get_continuity_index",
"mcp__continuity__get_continuity_test_contract"
],
"ask": [
"mcp__continuity__verify_continuity_proof"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as continuity. Review it before you use it.
Capability tags behind 3 rules
- mcp__continuity__get_continuity_index untrusted-input
- mcp__continuity__get_continuity_test_contract untrusted-input
- mcp__continuity__verify_continuity_proof untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.lumaion/continuity/verify?hash=24effdf22d6ad2cf889e00dc9ea0e16347b05802fb7a910184d4244c4d456dcc" | jq -e '.changed == false'Pinned hash 24effdf22d6a, from Nov 12, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.lumaion/continuity/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.lumaion/continuity)Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.
Lumaion Continuity MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Lumaion Continuity MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Lumaion Continuity MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Lumaion Continuity MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Lumaion Continuity MCP server have?
- 3 tools: 1 write, 2 read. verify_continuity_proof, get_continuity_index and get_continuity_test_contract.
Does the Lumaion Continuity MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Lumaion Continuity MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Lumaion Continuity MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.