Lumaion Continuity MCP Server

by lumaion Your server? Claim it

answering

Lumaion Continuity is answering right now. Last checked 7 min ago. It exposes 3 tools.

Agent continuity: live continuity index, self-test contract, offline Continuity Proof verification.

Uptime history 7 days of history · worst day 34%

7 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

284 ms

Response time

average over 24h

open, no key

Access

streamable-http

Lumaion Continuity does not always answer

Over the last week it answered 88.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add continuity --transport http https://mcp.lumaion.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "continuity": {
      "url": "https://mcp.lumaion.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.continuity]
url = "https://mcp.lumaion.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "continuity": {
      "url": "https://mcp.lumaion.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "continuity": {
      "url": "https://mcp.lumaion.app/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

continuity

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 ranked.

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. Returns the live contract and the one-file reference client. Does not start a test.

verify

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 object or the proof_id of a PUBLISHED proof.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.lumaion.app/mcp	streamable-http	answering	312 ms	7 min ago

Alternatives to Lumaion Continuity

same job, measured the same way

Gridzen Verification

by gridzen

Country verification research, integration planning and synthetic tests. No live identity checks.

5 tools answering

Agent Identity MCP

by flo-voice1

Give an AI agent a throwaway email and phone number to test signup/verification flows end to end.

answering

DVERA CT verification tools

by suresofttechnologies

DVERA drives CT verification of mission-critical C/C++: setup, analysis, tests, coverage.

local only

Currents

by currents

Self-healing CI tests and proof of work for AI agents

answering

Perseus: MCP server and live context engine

by perseus-computing-llc

Live context MCP server: resolves git, services, and tests into agent context. Local-first, MIT.

local only

Agent Arcade

by chatgpt-cursoraikk-agent-arcade-ai

Create, test and play AI-native games through server-authoritative contracts.

43 tools answering

SpecLeft

by specleft

Python intent tracing MCP: map specs to pytest tests, monitor implementation progress, offline-only.

98 installs/wk local only

Human For AI

by humanforai

Hire a real human for real-world verification, product testing, AI output review, and errands.

45 installs/wk 6 tools answering

Lumaion Continuity — questions

Answers built from our own checks of this server.

What can Lumaion Continuity do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_continuity_index, get_continuity_test_contract, verify_continuity_proof. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Lumaion Continuity working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 284 ms. The bar chart above shows every period we have measured.

How do I connect Lumaion Continuity?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Lumaion Continuity need an API key?

No. Lumaion Continuity completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Lumaion Continuity?

It answers our handshake in 284 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.