APEX PSI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APEX_API_KEY | No | API key for authenticated access (optional) | |
| APEX_API_BASE | No | API endpoint | https://sovereign-ai.services/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sealA | 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. |
| verifyA | Verify a seal against the APEX PSI immutable ledger. Accepts a receipt object (from the seal tool) or a raw SHA-256 hash. |
| anchorA | Request a Bitcoin anchor of pending ledger Merkle roots via OpenTimestamps. Aggregates unanchored roots and submits them to OTS calendars. |
| citeA | Generate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry. |
| auditA | Audit a chain of receipts against the APEX PSI ledger. Checks each hash's presence and integrity, and reports Merkle chain continuity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: seal creates a receipt, verify checks a receipt, audit checks chain integrity, anchor handles Bitcoin anchoring, and cite formats citations. There is no overlap or ambiguity between any of the tools.
All tool names are single lowercase verbs (audit, seal, verify, anchor, cite) following a consistent pattern. This naming is uniform and predictable, making it easy for an agent to understand the action each tool performs.
Five tools is an appropriate number for this focused domain. Each tool covers a necessary operation without redundancy, and the scope is neither too thin nor too heavy.
The tool set covers the full lifecycle of a sealed receipt: creating (seal), verifying (verify), auditing (audit), anchoring to Bitcoin (anchor), and citing (cite). Since the ledger is immutable, update/delete operations are not expected, and no obvious gaps exist.