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 provenancetibet-triage— Process triage with HITLtibet-ipoll-mcp— AI-to-AI messaging MCP servertibet-pol— Machine health monitoring
License
MIT — HumoticaOS
Metadata
Release files for tibet-phantom-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tibet_phantom_mcp-0.1.1.tar.gz | 5.2 kB | Without provenance | Details for tibet_phantom_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tibet_phantom_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for tibet_phantom_mcp-0.1.1-py3-none-any.whl |
Total release size: 11.9 kB
Release files / tibet_phantom_mcp-0.1.1.tar.gz
| Download URL | tibet_phantom_mcp-0.1.1.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
696b09dc2000caaa049bb83d2529ecf922a425a01cd5bc06113ba29d2623909c
|
|
BLAKE2b-256 checksum How to use checksums |
b58876df7ceb0a6e57a96cf10eb3fa48e378ac814d067b4d7e7a1e43e10bc397
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / tibet_phantom_mcp-0.1.1-py3-none-any.whl
| Download URL | tibet_phantom_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ab9f44b8d688932b21646b03457338242a22856ded8f372a7c4e115fef4f048
|
|
BLAKE2b-256 checksum How to use checksums |
59f6c61fe859857da7ee06d024b2a2ab58cdfea96e8dd052c0ecf5065d361de2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for tibet-phantom-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.