APEX PSI
NPM · APEX-PSI-MCP
Cryptographic truth infrastructure for AI agents: seal, verify, anchor, cite, audit.
Available components
Last scanned (12 hours ago)
Scores higher than 82% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 368 tokens (~73/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Analysed npm/apex-psi-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
anchor Anchor to Bitcoin ~60
Request a Bitcoin anchor of pending ledger Merkle roots via OpenTimestamps. Aggregates unanchored roots and submits them to OTS calendars.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | 'anchor' submits pending roots; 'status' checks anchor state (default: anchor) |
No output schema declared.
No examples provided.
audit Audit receipt chain ~50
Audit a chain of receipts against the APEX PSI ledger. Checks each hash's presence and integrity, and reports Merkle chain continuity.
| Name | Type | Req | Description |
|---|---|---|---|
| receipts | array | yes | Array of receipt objects to audit (in order) |
No output schema declared.
No examples provided.
cite Generate citation ~62
Generate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Citation format (default: apa) |
| receipt | object | yes | A receipt object as returned by the seal tool |
No output schema declared.
No examples provided.
seal Seal content ~116
Stamp a cryptographic receipt on content. Writes to the APEX PSI immutable ledger with SHA-256 hash, Ed25519 signature, and post-quantum LMS-W4-SHA256 signature.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to seal (text, up to 10000 characters) |
| context | string | – | Optional context label (e.g. document name, case ID) |
| model_id | string | – | Optional model/agent identifier producing the seal |
| predicate | string | – | Optional predicate describing why this is sealed |
No output schema declared.
No examples provided.
verify Verify receipt ~80
Verify a seal against the APEX PSI immutable ledger. Accepts a receipt object (from the seal tool) or a raw SHA-256 hash.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | – | A SHA-256 hash to look up in the ledger (with or without 'sha256:' prefix) |
| receipt | object | – | A receipt object as returned by the seal tool |
No output schema declared.
No examples provided.
How do I install the APEX PSI MCP server?
APEX PSI runs locally as an npm package, launched with npx -y apex-psi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · apex-psi-mcp
claude mcp add kawal393-apex-psi-mcp -- npx -y apex-psi-mcp
What is the APEX PSI MCP server?
APEX PSI is an MCP server listed in the public MCP registry as io.github.kawal393/apex-psi-mcp. Cryptographic truth infrastructure for AI agents: seal, verify, anchor, cite, audit. This page covers its npm package (apex-psi-mcp).
Is the APEX PSI MCP server safe to use?
APEX PSI scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the APEX PSI MCP server expose?
APEX PSI exposes 5 tools: seal, verify, anchor, cite, audit. Their descriptions and schemas cost roughly 368 tokens of context every time the server is loaded.
Is the APEX PSI MCP server still maintained?
APEX PSI is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the APEX PSI MCP server under?
APEX PSI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.