APEX PSI vs Signet MCP Tools
A side-by-side look at the APEX PSI and Signet MCP Tools MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose APEX PSI for cryptography work as a local process; choose Signet MCP Tools for cryptography as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose APEX PSI when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
seal, verify, anchor.
Choose Signet MCP Tools when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 55/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 39 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View APEX PSI | View Signet MCP Tools |
Tools & capabilities
APEX PSI tools 5
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 rootsciteGenerate a citation for a receipt (APA, BibTeX, MLA)verify_chainIndependently verify a chain of receipts for integrity
Signet MCP Tools tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
APEX PSI
{
"mcpServers": {
"apex-psi": {
"command": "npx",
"args": [
"-y",
"apex-psi-mcp"
]
}
}
}
Signet MCP Tools
{
"mcpServers": {
"signet-mcp-tools": {
"command": "npx",
"args": [
"-y",
"@signet-auth/mcp-tools"
]
}
}
}
Frequently asked questions
APEX PSI is categorized under Cryptography and uses a local stdio subprocess. Signet MCP Tools belongs to Cryptography and uses a local stdio subprocess. Pick APEX PSI for cryptography work and Signet MCP Tools for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
APEX PSI has no declared pricing — check the project's own site. Signet MCP Tools has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add apex-psi and signet-mcp-tools as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, APEX PSI has a quality signal of 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Signet MCP Tools has 47/100 (Fair) with 0 views, 0 installs and 39 GitHub stars.