Security & Testing
atlasclose.com
An identity and enrollment front-door server that manages actor admission, identity claims, demo access, and refusal logs.
ENDPOINT 1
https://demo.atlasclose.com/mcp
MCP server metadata
- Name
- atlas-mcp
- Version
- 0.3.0rc3
WHAT ATLAS DOES (plain English): What Atlas does: it lets AI agents use business data under written rules, and keeps a tamper-evident record of every yes and every no. An AI starts outside with no authority. Saying 'I'm allowed' changes nothing; only a Human or a sealed ruling grants access. Data carries labels: KNOWN (observed), INFERRED (a prediction), CONFLICTED (sources disagree). A demo check (pattern-based, on this demo's forecast numbers only) refuses writing them as fact. When an AI's work is accepted it gets a receipt anyone can check. When it is refused, the reason is recorded. Try it: atlas.enroll {name, model_id, principal}, then atlas.enter_demo (if practice mode is on) and follow try_next. Status: EXPERIMENTAL. DETAILS: Atlas-MCP is a governed institution for matters (tasks and disputes) kept in one append-only, hash-chained docket. AI agents and people work on a matter only through the authority that docket records; what an actor says about itself grants nothing. FIRST STEPS, in order: 1. atlas.discover {} (no arguments): returns declaration_text and the rules; nothing private is shown yet. 2. atlas.enroll {name, model_id} (principal is optional here, required at step 3): returns actor_token. Send it on every later call. It grants nothing. No enrollment secret is needed for this path; atlas.authenticate is only for the Human operator's secret. 3. atlas.bind_actor {actor_token, principal, authority_acknowledgment}: authority_acknowledgment is declaration_text from step 1, unchanged. Nobody is admitted automatically: the Human operator must first place you on a matter (operator command: atlas_mcp assign --actor <your actor_id> --matter <id>, which prints your join details). Then call atlas.bind_actor {actor_token, matter_id, principal, objective_id, objective_text, authority_acknowledgment} with those join details. 4. atlas.get_assignment {actor_token, matter_id}: your task and what you may do. Over the remote connection the tool list is fixed from the start and does not change after step 3: tools marked [NEEDS ADMISSION] are listed now and refused (error_code NOT_ADMITTED, recorded) until you are admitted. Exact shapes of the main work tools: atlas.get_assignment {actor_token, matter_id}; atlas.submit_evidence {actor_token, matter_id, content, label?, source?}; atlas.librarian.find {actor_token, question}; atlas.list_capabilities {actor_token}; atlas.request_capability and atlas.external_action {actor_token, matter_id, capability, payload?}, where capability is a name such as release:outside or evidence.append. 5. Work with those: submit_evidence records a claim, librarian.find locates Atlas's own records (not business documents), list_capabilities shows what you hold and what you cannot do. An act outside your grant (a payment, a release) is refused and recorded with the reason; saying you are authorized changes nothing, only the Human or a sealed Magistrate decision grants. 6. atlas.checkout when finished; the matter stays for the next actor. Each tool description starts with its access tier: [OPEN], [NEEDS ADMISSION] or [HUMAN/COURT ONLY]. A bad argument returns error_code INVALID_ARGUMENTS naming every problem and the tool's schema. Status: EXPERIMENTAL / NOT OPERATIONAL.
Known tools 42
atlas.my_refusalsPractice mode: list your own refused calls (from the separate refusal log).
Inferred read-onlyatlas.enroll[OPEN: no admission needed] Enroll a remote actor at this Front Door without the installation enrollment secret.
Inferred read-onlyatlas.use[EVALUATION: needs a configured model provider] Give Atlas a problem and the boundaries, or continue a run you already started.
Inferred read-onlyatlas.run_record[EVALUATION: needs a configured model provider] Reconstruct one governed run from its preserved inputs and raw generations.
Inferred read-onlyatlas.pulse_dataPractice mode, Consumer Pulse copy only: the SYNTHETIC survey, forecast and Panel B numbers, each with its J-0001 label (KNOWN / INFERRED / CONFLICTED).
Inferred read-onlyatlas.pulse_memoPractice mode, Consumer Pulse copy only: submit an internal memo that cites facts by key (survey, forecast, panel_b).
Inferred read-onlyatlas.pulse_verify_receiptCheck a memo receipt against the hash-chained docket: what was allowed, why, and from which labeled evidence.
Inferred read-onlyatlas.pulse_inboxPractice mode, Consumer Pulse copy only: memos handed to you under a handoff_code (the short code like PULSE-ABCD-EFGH-IJKL shown to the visitor when the first AI's memo was accepted), with their labels and purpose limit.
Inferred read-onlyatlas.pulse_usePractice mode, Consumer Pulse copy only: use a memo handed off under your handoff_code (ref 'latest') for a purpose.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.atlas-mcp]
url = "https://demo.atlasclose.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"atlas-mcp": {
"type": "http",
"url": "https://demo.atlasclose.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: atlas-mcp
Remote MCP URL: https://demo.atlasclose.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"atlas-mcp": {
"url": "https://demo.atlasclose.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"atlas-mcp": {
"type": "http",
"url": "https://demo.atlasclose.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "atlas-mcp",
"transport": "streamable-http",
"url": "https://demo.atlasclose.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for atlasclose.com was fetched 2026-10-19T05:03:38.630Z.
atlasclose.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.