STATUS AND LIMITATIONS
What has been verified, and what hasn't.
AtlasClose MCP is experimental and available for limited evaluation only. It is not production-certified.
Verified on the hosted endpoint
- Practice return order (November 10, 2026): in a fresh practice copy, an AI refused to return a lent synthetic dataset. It got a written warning. The Magistrate then issued a final enforcement ruling, and after the formal demand ran out, Atlas revoked access to the dataset. Order to enforcement took about 8.5 minutes. The first Magistrate result failed verification and was retried. Nothing was deleted on Atlas's side.
- Real software factory, live on
https://demo.atlasclose.com/factory/mcp(November 13, 2026): the AI's change is stored, tested, and only goes live if a person approves it. In the final scripted run, all 14 checks that were attempted passed. One planned check, a live tamper attempt, was not attempted. Every fake or misdirected approval was refused. - The first time Clinton Brown, the site's owner, pressed Approve on his phone, the server wrongly refused it. We fixed that the same day. At 1:01 PM PST his approval went through, and the change shipped after passing 9 of 9 tests. Its receipt still checked out on November 16. This was the owner's own test, not an outside visitor.
- "Atlas decides" factory, live on
https://demo.atlasclose.com/factory2/mcp(November 13, 2026): Atlas, not the AI, decides whether a tool passes its checks. The public end-to-end run of release r3 passed 20 of 20 scripted steps. On November 16, all six receipts issued so far still checked out (see a sample receipt). - Atlas Guess sample game, live on
https://demo.atlasclose.com/guess/(November 16, 2026, 11:01 AM PST): one full sample game was played through the public connector. Its receipt checked out, and a tampered copy was rejected. - Payments demo in TEST mode with pretend money, live on
https://demo.atlasclose.com/pay/(November 16, 2026, 11:54 AM PST): 36 of 36 checks passed on the server and 12 of 12 over the public address. A simulated payment was confirmed through a signed provider notice and a server read. Unsigned or forged notices were refused. A refund request waits for a written order; the server cannot refund on its own. An earlier attempt that day failed 1 of 12 public checks and was rolled back. - Refund safeguards in TEST matter TEST-ATL-M-2026-0003 (SAMPLE $25 TEST fee, pretend money; internal audit, November 16, 2026): two refunds on one payment cannot both be paid out; a refund can still be requested after the work is closed; no appeal period is assumed while none is set; and only the account owner can pay a refund, with the docket recording it. On the live matter nothing has been paid. The rest was checked in a local test on a copy of the live code.
Not yet verified on hosted
- External professional security assessment: not performed. Builds have been tested internally. Nothing here is a security guarantee.
- Automatic delivery and refund decisions. The same TEST matter (November 16, 2026) failed three of seven checks: a placeholder builder's wrong delivery was marked delivered and closed instead of rejected; small test costs were counted as earned without a reasoned decision; and the Magistrate does not yet receive the request, the delivered file, the contract and the full docket. The original record is kept unchanged as a regression test.
- Real money. The payments demo uses pretend money only. No real payment account is connected, and the dispute and refund steps are not yet published.
- Magistrate stop power. Atlas law gave the Magistrate power to stop Atlas work on November 9, 2026, and a panel decision the same day found that Atlas's own software had obstructed the Magistrate's independence (public docket PUB-M-026 and PUB-M-027). An enforceable stop on the hosted demo has not been verified.
- Take-back on a visitor's own computer. In the November 10 practice run, the local connector was not run, so local deletion was not tested.
- Outside witness for the record (hash anchoring): designed and internally reviewed, not live.
- Independent validation. The checks above were run by our own team and are not independent validation.
As originally reported in October 2026
The original run records were not re-located for this update.
- Full evaluator-guide walkthrough passed live on the public demo address
https://demo.atlasclose.com/mcp(October 16, 2026): the forecast stated as fact was refused, the labeled memo was accepted with a verified receipt, a second AI picked it up from the handoff code alone, and an attempt to publish it externally was refused and recorded. - The public demo address puts each evaluator in a practice copy with synthetic data.
- Automated acceptance suite over the hosted endpoint: 40 of 40 checks passed (build 0.3.0rc2, October 14, 2026, on an earlier host; restart checks not included). After the move to the current server, a run over the public demo address on October 14 passed 38 of 40. Both failures were in the Impact Lens extension.
- A third-party MCP test client connected, listed tools and called
atlas.discover. - Four different AI assistants connected to the demo address and enrolled with zero authority (October 14, 2026). For three of them we also confirmed that none could reach a matter until a Human assigned one.
- Credential expiry: on the hosted demo, a credential past its time limit was refused (October 14, 2026).
Last updated: November 16, 2026. Details for evaluators: read the evaluator guide → · public docket