# APEX PSI [Health: Active]

**Category:** 🔑 Cryptography  
**Repository:** https://github.com/kawal393/apex-psi-mcp-server  
**GitHub Stars:** 1  
**npm Downloads (last month):** 369  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/apex-psi

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

## Tools
Capabilities this server exposes over MCP:

- **seal** — Stamp a cryptographic receipt on content. Writes to the APEX PSI append-only ledger with SHA-256 hash, Ed25519 signature, and post-quantum LMS-W4-SHA256 signature. Proves existence and integrity at a point in time — not the truth of the contents.
- **verify** — 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.
- **anchor** — Read the Bitcoin (OpenTimestamps) anchoring state of the ledger's pending Merkle roots, or — only when action:'anchor' is passed explicitly — request that pending roots be aggregated and submitted to the OTS calendars. Defaults to 'status' (read-only) so a routine call never triggers a batch write. An anchor becomes confirmed only when a real Bitcoin block is found.
- **cite** — Generate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry.
- **verify_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.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What APEX PSI MCP server does

The APEX PSI MCP server gives an MCP-capable agent access to a provenance workflow built around cryptographic receipts. It records content through a sealing operation, then provides tools for checking the resulting receipt, checking related receipts as a chain, viewing anchoring status, and producing bibliographic citations.

The service is intended to establish that a record existed and remained unchanged at a point in time. It does not evaluate the factual accuracy of the record, certify its contents, or provide advice. Verification is based on cryptographic evidence and the service's append-only ledger.

## How it works

The listed cryptographic scheme includes SHA-256, Ed25519, and post-quantum LMS-W4. The `verify` tool checks whether the receipt's hash is present in the append-only ledger, allowing an agent to test the receipt's integrity.

The `anchor` tool reports Bitcoin anchoring status by default and can request anchoring for pending roots. The `cite` tool turns a receipt into a citation in APA, BibTeX, or MLA format. For related records, `verify_chain` independently checks a chain of receipts for integrity. Receipts include a link to the public verifier at `https://apex-infrastructure.com/verify`.

## Setup and configuration

Add the server to an MCP client using the `npx` command and the `apex-psi-mcp` package:

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

The package can also be installed locally with `npm install apex-psi-mcp`. Configuration variables are optional. `APEX_API_BASE` changes the API endpoint from its default of `https://apex-infrastructure.com/api`, while `APEX_API_KEY` supplies an API key for authenticated access.

## Tools and capabilities

The APEX PSI MCP server exposes five tools:

- `seal`: Creates a cryptographic receipt for content.
- `verify`: Checks a receipt against the append-only ledger.
- `anchor`: Reads Bitcoin anchoring status or requests anchoring of pending roots.
- `cite`: Generates APA, BibTeX, or MLA output for a receipt.
- `verify_chain`: Checks a receipt chain independently for integrity.

These operations suit workflows that need an agent to preserve provenance, check whether a receipt is recorded, inspect external anchoring, or attach a standard citation to recorded material.

## Limitations and notes

APEX PSI provides verification infrastructure, not a truth judgment. A successful integrity check shows that the relevant cryptographic record matches the ledger; it does not show that the underlying content is accurate or reliable. Bitcoin anchoring status is available through the `anchor` tool, but the material does not specify timing or guarantees for pending anchors. API authentication is available through `APEX_API_KEY`, but both documented environment variables are optional.

_Full upstream README: https://allmcps.com/mcp/apex-psi/readme_