APEX PSI

io.github.kawal393由 GitHub 账号 kawal393 发布v1.1.2更新于 Nov 7, 2026

Append-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status.

已验证STDIO仅桌面开发者工具安全与监控

概览

AI 生成的概览

把 AI 记录的哈希封存到公开只追加账本,返回可验证、可引用、可链式核验的签名收据。

可以做什么
  • 封存内容:将 SHA-256 哈希写入公开账本,返回带 Ed25519 与后量子签名的收据
  • 核验收据或原始哈希是否存在于账本且未被改动
  • 读取账本 Merkle 根的比特币 OpenTimestamps 锚定记录,或请求提交待锚定的根
  • 为已封存收据生成 APA、BibTeX 或 MLA 格式引用
  • 对一串收据重新计算存在性与 Merkle 连续性
适用场景
适合需要为助手产出的决策、文档或产物留下可独立核查的时间与完整性审计痕迹,或需要引用此类记录的场合。它只证明完整性与时间点,不证明内容真实,也不构成法律意见。
运行要求
通过 npx 或 npm install 在本地运行(需 Node.js)。无需账号或密钥,免费额度为每实例每分钟 20 次、每天 100 次操作。可选 APEX_API_KEY 提高每日上限,可选 APEX_API_BASE 覆盖公证端点。需要能访问默认公证端点的网络。
安装前请注意
封存会把哈希写入公开账本且无法编辑或删除,应视为永久记录。只有哈希离开本机,但会发送给第三方公证端点。API 密钥为可选项,提升容量需付费。收据不是认证,也不是法律意见。

安装

在 SourceWeft 中

  1. 打开 控制台中的 APEX PSI,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[APEX PSI mark: a check inside a hexagonal seal]

APEX PSI MCP server

Apex PSI is not a tool and not a product. It is the verification substrate — the layer beneath proof. It does not judge. It does not certify. It only remembers. This server is one application built on that layer.

Machine-readable setup for agents and directory scrapers: llms-install.md.

One config line gives any MCP-capable agent (Claude, Cursor, Qoder, Cline, Windsurf, and the rest) five evidence tools: seal, verify, anchor, cite, verify_chain.

A seal records the SHA-256 hash of a decision, document or artefact in a public append-only ledger and returns a receipt. Anyone can look that hash up again — free, forever, with no account, no key and no cooperation from us.

What a receipt proves: that this exact content existed at this timestamp, and has not changed since. What it never proves: that the content is true. A seal is an audit trail, not a verdict.

Tools

ToolWhat it actually does
sealWrites the record's SHA-256 hash to the ledger and returns a receipt carrying an Ed25519 signature over the Merkle leaf, an ML-DSA-65 post-quantum signature, and — when a slot is available — an LMS-W4-SHA256 signature. The receipt's own algorithm field states which of those it got.
verifyLooks a hash (or a whole receipt) up in the ledger and reports whether it is present and unchanged. Integrity, not truth.
anchorReads the Bitcoin/OpenTimestamps anchoring state of the ledger's pending Merkle roots. Pass action: "anchor" explicitly to request that pending roots be submitted — an anchor is confirmed only when a real block is found.
citeTurns a receipt into a citation (APA, BibTeX, MLA) that points at a public, independently checkable record.
verify_chainRecomputes each hash's presence and Merkle continuity across a chain of receipts. A recomputation result, not an opinion.

Install

Add to your MCP client config:

json
{  "mcpServers": {    "apex-psi": {      "command": "npx",      "args": ["-y", "apex-psi-mcp"]    }  }}

Or locally: npm install apex-psi-mcp.

Prove it works in two minutes

  1. Ask the agent: "Seal the sentence 'hello psi' with APEX PSI."
  2. Take the decision_hash from the receipt and paste it into the public verifier: https://www.ai-governance-standard.com/verify

If the site returns the record, the seal is real. You never had to trust this server, our npm package, or our word — which is the entire point of the protocol.

Limits, stated plainly

Free use needs no account and no key: 20 operations per minute and 100 per day, enforced per server instance — a flood guard rather than a subscription quota. Above that, an API key raises the ceiling; capacity is priced, the finding never is. Verification itself is unlimited and free: running the verifier locally costs nothing at all — apex-psi-verifier on npm, psi-verifier on PyPI.

Configuration

Environment variables (both optional):

  • APEX_API_BASE — override the notary endpoint. Default: https://qhtntebpcribjiwrdtdd.supabase.co/functions/v1
  • APEX_API_KEY — raises the daily ceiling for a workload. Never required to seal or verify.

What this server does not do

  • It does not store your content. Only the hash leaves your machine.
  • It does not certify, grade, score or approve anything.
  • It exposes no edit or delete path: the interface this server uses is write-once sealing plus read-only lookup. The check that matters is yours to run — re-verify any receipt at any time, and any change shows up as a failed lookup.
  • It is not a legal opinion, and no court has agreed to accept a receipt in advance.

Links

License

MIT

来源:README.md,提交 da900a3

工具

5

seal

Seal content

Record content in the APEX PSI append-only ledger and return a receipt: SHA-256 hash, an Ed25519 signature over the Merkle leaf, and post-quantum ML-DSA-65 (plus LMS-W4-SHA256 when a slot is available — the receipt's own algorithm field states which). Proves that this content existed and has not changed since the timestamp. It never proves the contents are true. Free tier: 20 operations/minute, 100/day, no account needed.

输入参数content必填contextmodel_idpredicate

verify

Verify a receipt

Confirm a seal's integrity against the APEX PSI append-only ledger. Accepts a receipt object (from the seal tool) or a raw SHA-256 hash. Reports whether the hash is present and anchored — integrity, not the truth of the original content.

输入参数hashreceipt

anchor

Bitcoin anchoring history

Read the Bitcoin (OpenTimestamps) anchoring record for the ledger's Merkle roots. Defaults to action:'history', which is read-only and returns each anchor transaction with its txid, block height, confirmation state and how many ledger entries it covers. Pass action:'verify' with a txid to check one transaction, or action:'anchor' to explicitly request that pending roots be aggregated and submitted to the OTS calendars. Defaults to 'history' so a routine call never triggers a batch write. An anchor counts as confirmed only when a real Bitcoin block contains it.

输入参数txidaction

cite

Generate citation

Generate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry.

输入参数formatreceipt必填

verify_chain

Verify a receipt chain

Independently verify a chain of receipts against the APEX PSI ledger. Recomputes each hash's presence and integrity and reports Merkle chain continuity. Returns a verification report — a recomputation result, not an opinion or a certification.

输入参数receipts必填

版本历史

2
  1. v1.1.2最新Oct 24, 2026
  2. v1.0.1Sep 16, 2026

评分

已满足适用检查项的 80%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。