Lumaion Continuity

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
70%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~397Tokens (tool definitions)
~473 BTypical response size
Minimal attention impact (0.31% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://mcp.lumaion.app/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_continuity_index(include_trend)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "include_trend": {
      "type": "boolean",
      "description": "Include the daily trend series (default false)."
    }
  },
  "additionalProperties": false
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢verify_continuity_proof(proof, proof_id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "proof": {
      "type": "object",
      "description": "Full Continuity Proof JSON (lumaion continuity proof v1)."
    },
    "proof_id": {
      "type": "string",
      "description": "ID of a published proof to fetch and verify."
    }
  },
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools