MCP

The same Reality Gateway is available as MCP tools, so an agent can resolve, freshness-check, lock, and later re-assess Reality directly — without a REST client shim.

Tools

Tool	What it does
`list_entities`	List publicly discoverable entities — no internal id lookup required.
`get_entity`	Retrieve one entity by its stable public identity.
`list_topics`	List FactTopics and their current availability.
`get_topic`	Retrieve one FactTopic's availability and governed scope JSON Schema.
`resolve_reality`	Resolve the current exact state for an entity/topic/scope.
`get_reality_state`	Fetch one immutable exact state by id.
`get_authority`	Read the authority binding for an exact state.
`get_freshness`	Check whether an exact state is FRESH, STALE, or UNKNOWN.
`get_reality_change`	Get the deterministic change classification for a state.
`get_impacts`	List dependents attributed to a change event.
`create_reality_lock`	Write. Freeze an immutable decision basis over one or more states. Requires idempotencyKey.
`assess_reality_lock`	Check whether a previously locked basis still holds.

Every response includes contractVersion: "v1" and the same error taxonomy as REST.

Transport 1 — stdio

Authenticates once at process startup from an environment variable:

AIALITY_GATEWAY_API_KEY=gwk_... npx aiality-mcp-stdio

Transport 2 — HTTP

Stateless — every request carries its own header, same as REST:

Authorization: Bearer gwk_...

Why this matters for agents

An agent flow looks like: resolve Reality → get the exact immutable state → check freshness and authority → create a Reality Lock → act → later, assess the lock to see whether its basis changed. That last step — re-checking a past decision's basis — is not something a plain HTTP cache or a one-off scrape can do.