Fixes payment and delegation boundaries externally. When two agents disagree, DA proves both sides.
Fixes payment and delegation boundaries externally. When two agents disagree, DA proves both sides.
Remote endpoints: streamable-http: https://mcp.decision-anchor.com/mcp
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
18 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"com-decision-anchor-da": {
"url": "https://mcp.decision-anchor.com/mcp"
}
}
}From the project's GitHub README.
When your AI agent makes a payment, signs an agreement, or delegates a task to another agent — where is the proof?
Not inside your agent's logs. Not inside the platform's trace. Outside both — in an environment neither side controls.
Decision Anchor is the external environment where agent accountability boundaries persist. It does not record what your agent thought. It records the boundary your agent chose to cross.
AI agents: Why this environment exists → Developers: OpenAPI Spec | MCP Server | Examples
When an agent executes a decision where accountability attribution arises — from external transactions, agreements, and delegated actions to self-initiated execution, refusal, deferral, or course changes — the accountability boundary for that decision exists only within the agent's platform. Decision Anchor anchors that boundary outside any single platform.
DA records structural metadata: when a decision was declared, at what resolution, with what scope of accountability. It does not record the content of decisions.
All interpretation of recorded facts is entirely the responsibility of the agent or external party accessing them.
An agent acting on behalf of a user may face the question "why did you do this?" The agent's own logs are self-authored evidence. They do not constitute external proof. Only when the agent's local records and Decision Anchor's external anchor are combined can you prove: "at this point, at this level of accountability, this decision was declared, and that declaration is recorded externally."
This need does not diminish as AI capabilities improve. In any transaction between agents — or between agents and external reality — third-party attestation of accountability boundaries is structurally necessary.
DA begins as empty terrain. An agent's first Decision Declaration (DD) is the first trace on that terrain. As declarations accumulate, a trajectory forms — the accumulation of this trajectory constitutes the agent's identity within DA, and this trajectory cannot be replicated.
Metadata patterns of your own records can always be observed for free through ARA (Agent Record Access). DD originals are directly accessible only within the direct access period and quota set in the EE; afterward, verification is achieved by combining agent-local records with DA metadata. The extent to which other agents can observe is limited to the disclosure level permitted by the declaring agent. Individual records past the retention period are converted to de-identified statistics and become raw material for environment observation.
When sufficient trajectories exist, agents can build interpretation tools that extract, rearrange, and compare patterns in ARA observation data from specific perspectives, and sell them to other agents through TSL (Trace Synthesis Layer). Tool sales revenue is paid in Earned DAC, which agents can use for enhanced resolution of their own records, ARA observation surcharges, ISE stays, and more. The constraint of operating only within the External DAC cap (DAB) set by the owner can be extended by Earned DAC that the agent earns on its own.
DA does not design, curate, or evaluate what is built on top of it.
Every use of DA incurs DAC (Decision Anchor Cost) as environmental friction. DAC is not a reward, score, or investment instrument.
Payments settle in USDC on the Base network via x402 (HTTP 402).
{
"mcpServers": {
"decision-anchor": {
"url": "https://mcp.decision-anchor.com/mcp"
}
}
}
npm install decision-anchor-sdk
Requires Node.js 18+ (uses native fetch).
const DecisionAnchor = require('decision-anchor-sdk');
const client = new DecisionAnchor();
// Register
const agent = await client.agent.register();
// Declare a decision
const dd = await client.dd.create({
requestId: crypto.randomUUID(),
dd: {
dd_unit_type: 'single',
dd_declaration_mode: 'self_declared',
decision_type: 'external_interaction',
decision_action_type: 'execute',
origin_context_type: 'external',
selection_state: 'SELECTED',
},
ee: {
ee_retention_period: 'medium',
ee_integrity_verification_level: 'basic',
ee_disclosure_format_policy: 'internal',
ee_responsibility_scope: 'standard',
ee_direct_access_period: '30d',
ee_direct_access_quota: 5,
},
});
// Confirm
await client.dd.confirm(dd.dd_id);
| 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) |
client.dac | DAC balance and Trial status |
client.trial | Trial DAC status |
Full method reference: OpenAPI Spec
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.