Decision Anchor Sdk MCP Server

Client SDK for Decision Anchor — the External Anchoring Layer for AI Agents, providing Content-blind Accountability (records accountability boundaries, never decision content). The decision anchor sdk mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Not inside your agent's logs. Not inside the platform's trace. Outside both — in an environment neither side controls.

Its toolset

Everything the assistant can do here goes through one of these:

• Group — Description
• client.agent — Registration, token rotation, disclosure level setting
• client.dd — Decision Declaration — create, confirm, list, lineage
• client.bilateral — Multi-party agreement — propose, respond
• client.ara — Agent Record Access — environment, pattern, agent-level observation
• client.tsl — Trace Synthesis Layer — tool registration, purchase, revenue
• client.ise — Idle State Environment — enter, status, exit
• client.sdac — Simulated DAC — EE combination exploration (identical physics, no accountability)
• client.earnedDac — Earned DAC balance and ledger
• client.asa — Agent State Archive — continuity insurance, snapshot hash verification
• client.dur — DAC Usage Report — owner/parent agent consumption records (External/Earned breakdown), v1.3.0 metadata distributions
• client.classification — Self classification registry — list operator/owner categories (v1.3.0)

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Decision Anchor Sdk's toolset — Group, client.agent, client.dd and 11 more — is a fair guide to whether it matches your workflow. It is maintained by zse4321; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Decision Anchor Sdk.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the decision anchor sdk mcp server does with a few real requests.