APEX PSI

io.github.kawal393Published by GitHub account kawal393v1.1.2Updated Nov 7, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Seals hashes of AI records in a public append-only ledger and returns signed receipts you can verify, cite and chain-check.

What you can do
  • Seal content by writing its SHA-256 hash to a public ledger and get back a receipt with Ed25519 and post-quantum signatures
  • Look up a receipt or raw hash to confirm it is present and unchanged in the ledger
  • Read the Bitcoin/OpenTimestamps anchoring record for ledger Merkle roots, or request that pending roots be submitted
  • Generate APA, BibTeX or MLA citations for a sealed receipt
  • Recompute presence and Merkle continuity across a chain of receipts
When to use it
Useful when an assistant produces decisions, documents or artefacts whose existence and unchanged state at a point in time need an independently checkable audit trail, and when you want citations pointing at such a record. It proves integrity and timing, not truth or legal validity.
Requirements
Runs locally via npx or npm install (Node.js). No account or key needed: free use is limited to 20 operations per minute and 100 per day per instance. Optional APEX_API_KEY raises the daily ceiling; optional APEX_API_BASE overrides the notary endpoint. Network access to the default notary endpoint is required.
Before you install
Sealing writes a hash to a public ledger and cannot be edited or deleted, so treat it as permanent. Only the hash leaves your machine, but it is sent to a third-party notary endpoint. An API key is optional and paid capacity raises limits. Receipts are not a certification or legal opinion.

Installation

In SourceWeft

  1. Open APEX PSI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit da900a3

Tools

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.

Parameterscontentrequiredcontextmodel_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.

Parametershashreceipt

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.

Parameterstxidaction

cite

Generate citation

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

Parametersformatreceiptrequired

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.

Parametersreceiptsrequired

Version history

2
  1. v1.1.2LatestOct 24, 2026
  2. v1.0.1Sep 16, 2026

Score

80% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.