Skip to main content
Audact
See the offer

Model Context Protocol

Governance primitives as tools, for any client.

MCP host: In development

mcp://mcp.audact.ai

The public protocol surface: the host for the Model Context Protocol and the tools a client reaches across it. Not the REST host, which has its own entry, and not the endpoints used inside the current product.

Measured on 30 September 2026 with two independent resolvers: the Model Context Protocol host mcp.audact.ai does not exist in DNS. The same lookup returns records for our production hosts and nothing for an invented subdomain, so the answer belongs to the name and not to the resolver.

Why this status
Claim
In development · Not available
Scope
The public protocol surface: the host for the Model Context Protocol and the tools a client reaches across it. Not the REST host, which has its own entry, and not the endpoints used inside the current product.
Ground
Measured on 30 September 2026 with two independent resolvers: the Model Context Protocol host mcp.audact.ai does not exist in DNS. The same lookup returns records for our production hosts and nothing for an invented subdomain, so the answer belongs to the name and not to the resolver.
What it does not establish
That any individual tool behind this host works today. That is confirmed per tool, and the confirmation is open.
What you can get today
Nothing to order. Access runs through onboarding inside an applicable paid agreement; the protocol surface is not priced separately.
Last checked
30 September 2026
Where to check it
/mcp-server

Model Context Protocol: In development

The Audact platform is designed to speak the Model Context Protocol, so an agent could call governance as a tool: four tools that would call a subset of the documented endpoints. The host mcp.audact.ai does not resolve today, so nothing is enforced, emitted or queryable over MCP yet.

The four tools

get_disclosure_script(jurisdiction)
  → the Article 50 disclosure wording for DE, NL, FR, IT, ES, EN-GB, …

verify_consent(receipt_id)
  → lawful basis, scope and withdrawal status from the Consent Vault

attest_interaction(payload)
  → a receipt for the utterance, action or tool call, plus its Merkle path

query_evidence_chain(filter)
  → matching receipts and chain links within your own tenant

The tools call documented REST endpoints. A client that speaks Model Context Protocol does not need an SDK.

What a call looks like

{
  "method": "tools/call",
  "params": {
    "name": "attest_interaction",
    "arguments": {
      "interaction_id": "call_8h2k9d7",
      "modality": "voice",
      "article_50_clause": "1",
      "jurisdiction": "DE"
    }
  }
}

The response is the same compliance receipt the REST endpoint returns. One artefact, two ways in.

What it is

The generic surface: when available, any client that speaks the Model Context Protocol will connect to it.
In development
Designed to evaluate policy server-side, so a call that reaches the Audact server could not be argued past a rule.
In development
The four tools above, calling a subset of the documented endpoints.
In development
The endpoints those tools would call: Article 50 Attestation and Evidence Vault.
In development

The distinction

Two surfaces, one abbreviation.

This page describes the Audact platform server: the generic, multi-client entry point. The Anthropic connector is something else: a vendor-specific bridge into Claude Enterprise, layered on top, with organisation-level registration.

They get confused constantly, and the confusion is expensive: one is a protocol implementation anyone can use, the other is a registration inside one vendor's product. Each has its own page.

Why server-side

A tool an agent can argue with is not a control.

The policy is designed to run on our side of the protocol, for every call that reaches it. A call that never reaches the server is outside that boundary.

Questions

Which clients work with it?
In development. When available, any client that speaks the Model Context Protocol will connect to it. It is an open protocol, and our implementation against it is in development. No partnership is implied and none is needed.
Do I need this, or the REST API?
In development. When it ships, whichever fits your stack. The tools are designed to call the documented endpoints and produce the same receipts; the protocol will be a convenience, not a different product.
When does it ship?
It is in development and no date is committed. Tell us what you would connect it to and we will tell you where that sits in the order.

The endpoints, over REST

The endpoints these tools call are documented over REST, each with its own status; no public API is served on api.audact.ai yet, apart from the published Merkle roots. If you want the fuller description of the interface, that is the page.

See the API

Related