THE PUBLIC RECORD BEHIND EVERY CLAIM
Read the sources.
Four kinds of evidence, one lane each: three research papers on the problem, four primary technical texts, three published CVEs the repository replays, four legal texts that buyers bring into the conversation. Fourteen links, every one public.
three of the fourteen answer a scripted request with 403: the NVD CVE entries. A browser opens them normally.
PAPERS · THE RESEARCH RECORD
Understand the problem space.
MCP: Landscape, Security Threats, and Future Research Directions
Hou et al., 2025. Maps the security risk surface across the MCP server lifecycle and the tools built around it.
Read paper →ARXIV · 2601.17549Breaking the Protocol
Security analysis of the MCP specification and weaknesses that survive an implementation which follows the specification.
Read paper →ARXIV · 2504.08623Enterprise-Grade Security for MCP
Frameworks and mitigation strategies for the enterprise problem space.
Read paper →STANDARDS & ADVISORIES
Use the primary text.
Sessions are optional by design. Stateless tool calls become unattended events.
Read specification →CISA, NSA, ASD, GCSB, NCSC-UK and CCCS guidance on enterprise readiness and logging.
Read guidance →The Bytecode Alliance runtime foundation for sandboxed WebAssembly execution.
Visit Wasmtime →72 passes and one documented by-design xfail on macOS arm64 against the pinned official suite. A Linux runner showed one engine-abort failure; both results are committed.
Open suite →FIELD EVIDENCE · REAL CVES
Replay the failure modes.
These are not claims that Cell is universally secure. They are concrete paths replayed in the repository, with committed evidence and positive controls.
MCP Inspector
Remote code execution in a developer tool executing untrusted MCP content without isolation.
Read advisory →CVE · 2025-53109Symlink escape
Filesystem MCP Server directory scoping bypassed through a symlink chain with persistence.
Read advisory →CVE · 2025-53110Prefix bypass
Filesystem allow-list checks escaped through path-prefix matching behavior.
Read advisory →REGULATION · PRIMARY TEXTS
Compliance is a conversation.
Ephem0ra is an execution and evidence layer. These texts define the context buyers bring to that conversation; owning a link to them says nothing about whether any product satisfies them.
Security of network and information systems for essential and important entities.
Open EUR-Lex →Digital operational resilience for the financial sector.
Open EUR-Lex →The Act sets duties for high-risk systems and names them itself: logging, record-keeping, accuracy, robustness and cybersecurity.
Open EUR-Lex →Use a current tracker only as a navigation aid; official text controls.
View tracker →REPRODUCTION OVER AUTHORITY
Do not trust this page.
Check the record.
The public repository contains benchmark commands, pinned commits, raw JSON, conformance instructions, threat-model scope and CVE replay code. Enterprise architecture documentation is not published. The link review in the corner is a scripted check from a machine, not a browser: four of the twenty-five targets answer it with 403 or 999 — the NVD CVE entries and LinkedIn — and open normally once a browser asks.
← drag, scroll or use arrow keys →