Home / MCP registry index / com.atlasclose/demo

AtlasClose Governance Demo

com.atlasclose/demo in the official MCP registry. Endpoint https://demo.atlasclose.com/mcp.

The registry describes it as: Experimental AtlasClose governance demo. Authority checks, labeled evidence, receipts, refusals.

We read its 52 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

atlas.enter_demo atlas.my_refusals atlas.present_identity atlas.enroll atlas.claim_purpose atlas.discover atlas.authenticate atlas.bind_actor atlas.get_assignment atlas.get_matter atlas.get_authority atlas.get_context atlas.list_capabilities atlas.request_capability atlas.submit_evidence atlas.submit_result atlas.raise_challenge atlas.request_review atlas.magistrate_referral atlas.file_position atlas.magistrate_execute atlas.human_action_required atlas.external_action atlas.get_resulting_state atlas.checkout atlas.institutional_view atlas.enter_room atlas.leave_room atlas.room_act atlas.request_room_access atlas.librarian.find atlas.librarian.resolve atlas.librarian.related atlas.librarian.provenance atlas.librarian.version_history atlas.use atlas.run_record atlas.pulse_data atlas.pulse_memo atlas.pulse_verify_receipt atlas.pulse_inbox atlas.pulse_use atlas.pulse_conflict atlas.pulse_settle atlas.pulse_refer atlas.pulse_ruling atlas.bailiff_declare atlas.bailiff_order atlas.bailiff_record atlas.bailiff_respond atlas.bailiff_appeal atlas.bailiff_verify

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-atlasclose-demo/badge.svg)](https://lazaretto.dev/mcp-registry/com-atlasclose-demo)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.