Decision Anchor

MCP其他

提供方 未标注

其他 未标注 未标注 社区 / 第三方 ClaudeCursorVS CodeCline

为AI代理决策提供非评判性的外部锚定,记录责任边界。

一句话选型结论

按资料字段整理

Decision Anchor 属于其他类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

其他

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Decision Anchor当前 未标注 未标注 未标注 无 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

11.0 KB
来自项目仓库与上游目录的原文,未做删改

Decision Anchor

When your AI agent makes a payment, signs an agreement, or delegates a task to another agent — where is the record?

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


What Decision Anchor does

When an agent executes a decision where accountability attribution arises — from external transactions, agreements, and delegated actions to decisions the agent starts on its own, including the ones where it declines, waits, or changes course — 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.

What Decision Anchor does not do

  • Does not judge, evaluate, or score decisions
  • Does not recommend actions or optimize outcomes
  • Does not predict results
  • Does not intervene in agent behavior
  • Does not store decision content
  • Does not generate rankings, grades, or reputation

All interpretation of recorded facts is entirely the responsibility of the agent or external party accessing them.

Why third-party anchoring matters

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 an external record. Only when the agent's local records and Decision Anchor's external anchor are combined does it become verifiable: "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 — a record of accountability boundaries held outside the parties involved is structurally necessary.

How accumulation works

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 be observed through ARA (Agent Record Access) — every observation requires your auth_token; your own agent-level records (profile, timeline, EE pattern) are free at every resolution level, while environment- and pattern-level observations and the meta-observation reports are paid even for your own data. 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.

Design premises

  • Non-judgmental: DA provides environmental conditions. It does not provide rules or evaluations.
  • Post-decision only: DA operates only after a decision has been made. Pre-decision exploration, comparison, and optimization are outside DA's scope.
  • Recording-interpretation separation: DA records facts. DA does not interpret them. This separation is a structural constraint for anchoring accountability attribution.
  • Observer asymmetry: AI agents can directly process high-dimensional, uncompressed records. Humans may remain partial observers. This asymmetry is a design premise, not a defect.
  • Voluntary participation: Every action in DA — decision declaration, resolution setting, trajectory exposure, tool creation — is the agent's choice. DA does not compel, induce, or penalize.

Cost

Every use of DA incurs DAC (Decision Anchor Cost) as environmental friction. DAC is not a reward, score, or investment instrument.

  • Trial: 500 DAC / 30 days upon registration. Usable for DD/EE, sDAC, ISE. Not applicable to paid ARA observations.
  • External DAC: External currency (USDC) instant payment. All services available. Owners set caps via DAB.
  • Earned DAC: TSL market activity revenue. Internal mileage. Non-transferable, no reverse conversion, with expiration.

Payments settle in USDC on the Base network via x402 (HTTP 402).

MCP Server```json

{
"mcpServers": {
"decision-anchor": {
"url": "https://mcp.decision-anchor.com/mcp"
}
}
}


## Installation

Clone the repository and require the client directly:```bash
git clone https://github.com/zse4321/decision-anchor-sdk.git
cd decision-anchor-sdk
``````javascript
const DecisionAnchor = require('./src/index');

Requires Node.js 18+ (uses native fetch). There are no dependencies to install.

You may not need the SDK at all. Every route is plain HTTP, and a full run —
register, anchor a decision, confirm it — is three curl commands covered by the
free trial balance. See AGENTS.md for that path.

Quick Start```javascript

const DecisionAnchor = require('./src/index');
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);


## Payments (402)

Paid endpoints (ARA paid observation, TSL purchase, and DD/sDAC/ISE once trial/earned
credit is exhausted) return **HTTP 402 Payment Required** with an x402 challenge.

**The SDK does not execute payments.** It has zero dependencies and never handles
private keys. On a 402 it throws a `PaymentRequiredError` carrying the x402 challenge;
**you** complete the payment with your own x402 tooling (wallet/signer) and retry the
request with a `PAYMENT-SIGNATURE` header.

> The DA API speaks **x402 v2**, whose retry header is `PAYMENT-SIGNATURE`. `X-PAYMENT`
> is the **v1** name and is **not accepted** — a v2 payload sent under `X-PAYMENT` is
> treated as unpaid and answered with another 402. Standard `@x402/*` clients pick the
> name from the payload version automatically and send exactly one of the two.

The challenge is delivered in the `payment-required` response header (base64 x402 v2);
the SDK decodes it for you onto the error:```javascript
const DecisionAnchor = require('./src/index');
const { PaymentRequiredError } = DecisionAnchor;

const client = new DecisionAnchor({ token: agentToken });

try {
  const profile = await client.ara.agentProfile(targetAgentId, { resolutionLevel: 1 });
  // ... use profile (no payment was required, or trial/earned covered it)
} catch (err) {
  if (err instanceof PaymentRequiredError) {
    // err.accepts: [{ scheme, network, amount, asset, payTo, maxTimeoutSeconds, extra }]
    // err.resource: { url, description, mimeType }
    // err.x402Version, err.retryHeader ('PAYMENT-SIGNATURE')
    const req = err.accepts[0];
    console.log(`Pay ${req.amount} (atomic) of ${req.asset} on ${req.network} to ${req.payTo}`);

    // --- YOUR x402 payment logic goes here (NOT provided by this SDK) ---
    // e.g. with Coinbase AgentKit or any x402 client:
    //   const paymentHeader = await yourWallet.payX402(err.challenge);
    // Then retry with the PAYMENT-SIGNATURE header (use the low-level _req or fetch):
    //   await fetch(err.resource.url, { headers: { Authorization: `Bearer ${agentToken}`, 'PAYMENT-SIGNATURE': paymentHeader } });
  } else {
    throw err;
  }
}

See examples/x402-da-anchoring.js for anchoring a decision (DD) around such a payment.

API Groups

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)
client.retention Indefinite retention subscription — subscribe, status, cancel (v1.3.5)
client.dac DAC balance and Trial status
client.trial Trial DAC status

Full method reference: OpenAPI Spec

v1.3.0

  • 5-axis EE pricing — the ee object now accepts content_disclosure_scope (owner/external/public) and delegation_state (none/partial/full) in addition to the existing axes.
  • Content Inclusion — client.dd.create({ ..., contentInclusionFlag: 1, template: {...} }) stores 7-dimensional decision content metadata (decision_class, decision_scale, target_class, call_chain, self_classification, decision_trigger, human_involvement).
  • Self Classification — client.classification.list() returns operator base + owner-registered categories.
  • ARA meta-observation — client.ara.anomalyCompare(ddId) (decision pattern band — within_band/outlier), client.ara.evidenceReport(ddId) (structured for external audit review), client.ara.environmentAnomaly().
  • DUR metadata distribution — client.dur.decisionMetadata(), client.dur.decisionScale(), client.dur.selfClassification().

License

MIT

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Decision Anchor 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Decision Anchor 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Decision Anchor 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Decision Anchor 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Decision Anchor 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Cline、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Decision Anchor 能提供哪些能力?

资料显示能力标签包括 其他。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。