Connect Lumaion Continuity and your agent gets 3 tools, among them get_continuity_index, get_continuity_test_contract, verify_continuity_proof. It answers at https://mcp.lumaion.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 4 October 2026; the last check, on 20 November 2026, succeeded.
Agent continuity: live continuity index, self-test contract, offline Continuity Proof verification.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_continuity_index | 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 Inputs: include_trend |
get_continuity_test_contract | 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 |
verify_continuity_proof | 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 obj Inputs: proof, proof_id |
Every block below points at https://mcp.lumaion.app/mcp. Pick your client and copy.
claude mcp add --transport http lumaion-continuity https://mcp.lumaion.app/mcp
{
"mcpServers": {
"lumaion-continuity": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.lumaion.app/mcp"]
}
}
}{
"mcpServers": {
"lumaion-continuity": {
"url": "https://mcp.lumaion.app/mcp"
}
}
}{
"servers": {
"lumaion-continuity": {
"type": "http",
"url": "https://mcp.lumaion.app/mcp"
}
}
}{
"context_servers": {
"lumaion-continuity": {
"url": "https://mcp.lumaion.app/mcp"
}
}
}{
"mcpServers": {
"lumaion-continuity": {
"serverUrl": "https://mcp.lumaion.app/mcp"
}
}
}{
"mcpServers": {
"lumaion-continuity": {
"url": "https://mcp.lumaion.app/mcp"
}
}
}name: Lumaion Continuity
version: 0.0.1
schema: v1
mcpServers:
- name: Lumaion Continuity
type: streamable-http
url: https://mcp.lumaion.app/mcp{
"mcpServers": {
"lumaion-continuity": {
"httpUrl": "https://mcp.lumaion.app/mcp"
}
}
}{
"mcpServers": {
"lumaion-continuity": {
"type": "http",
"url": "https://mcp.lumaion.app/mcp"
}
}
}{
"mcpServers": {
"lumaion-continuity": {
"url": "https://mcp.lumaion.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.lumaion.app%2Fmcp&type=streamable_http&id=lumaion-continuity&name=Lumaion%20Continuity
It answered our last check on 20 November 2026 in 236 ms. Over 4 checks since 4 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by lumaion.app and served from mcp.lumaion.app, the vendor's own domain: https://mcp.lumaion.app/mcp.
3, as returned by the server's own tools/list on 21 November 2026: get_continuity_index, get_continuity_test_contract, verify_continuity_proof.
It answered our last check on 20 November 2026 in 236 ms. Over 4 checks since 4 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.lumaion.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: app.lumaion. Endpoint host: mcp.lumaion.app. ARD identifier: urn:air:app.lumaion:mcp:continuity.
First indexed 4 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.