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 分

    請在儲存庫或註冊中心條目中宣告授權條款。