APEX PSI

Cryptographic truth infrastructure for AI agents: seal, verify, anchor, cite, audit.

AI & MLTypeScriptv1.0.1

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 an application built on that layer.

Cryptographic truth infrastructure for AI agents.

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

This server proves the existence and integrity of a record at a point in time. It does not judge the truth of a record's contents. It is an independent verification service, not advice.

Tools

ToolDescription
sealStamp a cryptographic receipt on content (SHA-256 + Ed25519 + post-quantum LMS-W4)
verifyConfirm a receipt's integrity (hash present in the append-only ledger)
anchorRead Bitcoin anchoring status (default), or request anchoring of pending roots
citeGenerate a citation for a receipt (APA, BibTeX, MLA)
verify_chainIndependently verify a chain of receipts for integrity

Installation

Add to your MCP client config:

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

Or install locally:

npm install apex-psi-mcp

Configuration

Environment variables (optional):

  • APEX_API_BASE — API endpoint (default: https://apex-infrastructure.com/api)
  • APEX_API_KEY — API key for authenticated access

Usage

Once installed, your AI agent can:

  1. Seal content — "Seal this document with APEX PSI"
  2. Verify receipts — "Verify this receipt against the ledger"
  3. Check anchoring — "What is the Bitcoin anchor status of this seal?"
  4. Generate citations — "Cite this receipt in APA format"
  5. Verify a chain — "Independently verify this chain of receipts"

Every receipt carries a verify link to https://apex-infrastructure.com/verify — sealed arithmetic, public provenance.

Links

License

MIT

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y apex-psi-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

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

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

apex-psi-mcpnpm

Compatible MCP Clients

APEX PSI works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More