Skip to main content
Audact
See the offer

Connector · Anthropic

Governance as tools inside Claude Enterprise.

Planned · no date set

Planned: registered as an organisation-level tool provider in Claude Enterprise, Audact's own governance tools would be available inside it, and a call to one of those tools would get a gate decision and a receipt. It does not sit in front of other tools or servers.

The tool registration

{
  "server": "audact-anthropic",
  "protocol": "model-context-protocol",
  "organization": "anthropic-org:acme-eu",
  "tools": [
    "get_disclosure_script",
    "verify_consent",
    "attest_interaction",
    "query_evidence_chain"
  ],
  "policy_packs": ["aia-50", "gdpr"]
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

The same four tools as the platform surface. What the Anthropic connector adds is registration at organisation level, so an administrator enables it once instead of per agent.

What the connector will carry

Registration with Claude Enterprise as an organisation-level tool provider.
Planned
A governance gate before a call to one of the Audact tools, with the per-jurisdiction policy pack applied.
Planned
A receipt per turn, exportable into the compliance stack you already run.
Planned
The generic Audact platform surface over Model Context Protocol.
In development

Who it is for

The deployment that already exists.

An organisation running Claude Enterprise has agents in production. A tool-provider registration would add the Audact tools to the organisation: an administrator enables them once instead of per agent, and a call to one of those tools would get a gate decision and a receipt.

It is most relevant where the deployment is regulated (healthcare, financial services, legal, public sector) and least relevant where nothing the agent does can bind the organisation to anything.

Setup

Five steps, once the connector ships.

  1. Register the Audact server in your Claude Enterprise administration.
  2. Map your Anthropic organisation id to the Audact tenant.
  3. Configure the per-jurisdiction policy packs in the Audact policy engine.
  4. A call to one of the Audact tools would get a gate decision before it runs.
  5. Receipts are emitted per turn and exportable to your compliance stack.

Questions

How is this different from the Audact MCP server?
The platform server is the generic surface: when available, any Model Context Protocol client will connect to it (In development; no date set). This connector is a bridge specific to Claude Enterprise, layered on top, and would come with an organisation-level registration; no date set.
Is this an Anthropic partnership?
No. Model Context Protocol is an open protocol and our implementation against it is in development. Anthropic is named here as the vendor of the platform it bridges into, and nothing on this page should be read as an endorsement.

The same primitives, without the connector

A connector is a shorter path into one platform. Underneath it are six endpoints that run inside the managed platform, and an evidence chain that is identical either way.

See the API

Related