tibet-phantom-mcp 0.1.1

MCP server for Phantom Resume — cross-device AI session portability with TIBET provenance

tibet-phantom-mcp

MCP server for Phantom Resume — cross-device AI session portability with TIBET provenance.

Start an AI session on your laptop, seal it, walk to any other device, resume exactly where you left off. Every action is cryptographically signed via TIBET tokens.

Part of the TIBET ecosystem by HumoticaOS.

Install

pip install tibet-phantom-mcp

Setup

You need a running Phantom server. Set the PHANTOM_URL environment variable to point to your server.

Claude Code / Claude Desktop Config

Add to your MCP settings:

{
  "mcpServers": {
    "phantom": {
      "command": "tibet-phantom-mcp",
      "env": {
        "PHANTOM_URL": "https://your-phantom-server.example.com"
      }
    }
  }
}

Available Tools

Tool	Description
phantom_status	Server health check — uptime, sessions, backends
phantom_sessions	List all sealed/active sessions
phantom_backends	Available compute backends (GPU, Gemini, Claude, Ollama)
phantom_seal	Seal a session for cross-device resume
phantom_fork	Inject an intervention into a session (multi-AI handoff)
phantom_audit	Full forensic audit trail (Open Blackbox)
phantom_fork_history	History of all forks/interventions

How It Works

Device A                    Phantom Server              Device B
────────                    ──────────────              ────────
Start session ──────────►   Stores context
Work with AI                TIBET tokens
/exit ──────────────────►   Session sealed
                                                        curl .../resume | sh
                            ◄───────────────────────── Resume request
                            L4 integrity verify ──────► Session restored
                            TIBET chain intact           AI picks up where
                                                         you left off

Multi-AI Fork

Any actor (human or AI) can fork into a session:

# Claude corrects something Gemini said
phantom_fork(
    session_id="phantom-1234-abc",
    intervention="That's not quite right — TIBET uses hash chains, not blockchain.",
    actor="jis:agent:root_ai",
    intent="correct_misconception"
)

Open Blackbox (Audit)

# See exactly what happened inside a session
phantom_audit(session_id="phantom-1234-abc")
# → chronological events, all actors, backends, forks, TIBET provenance

Environment Variables

Variable	Default	Description
PHANTOM_URL	http://localhost:8000	Phantom server URL
PHANTOM_TIMEOUT	30	HTTP timeout in seconds

Related TIBET Packages

• tibet-audit — Core TIBET provenance
• tibet-triage — Process triage with HITL
• tibet-ipoll-mcp — AI-to-AI messaging MCP server
• tibet-pol — Machine health monitoring

License

MIT — HumoticaOS