TrustAtom MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TrustAtom MCP ServerSign this clinical triage decision for HIPAA compliance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
TrustAtom MCP Server
Cryptographic receipts for AI decisions. 5 minutes to your first receipt.
Every AI decision in your org is unsigned — and your auditor is going to ask about it. TrustAtom signs every decision with Ed25519 and returns a verifiable receipt in under 3ms.
Quick Start
git clone https://github.com/CWNApps/trustatom-mcp
cd trustatom-mcp
npm install
npm run keygen # Generate Ed25519 key pair
npm test # Run 8 eval testsAdd to Claude Desktop
{
"mcpServers": {
"trustatom": {
"command": "npx",
"args": ["tsx", "src/server.ts"],
"cwd": "/path/to/trustatom-mcp",
"env": { "TRUSTATOM_KEY_PATH": "./keys/trustatom_keys.json" }
}
}
}Then in Claude: "Sign this AI decision with TrustAtom" → receipt issued automatically.
Related MCP server: Openterms-mcp
What It Does
Tool | Description | When |
| Sign a decision, return receipt | At every AI decision point |
| Verify an existing receipt | During audit, dispute resolution |
| Query the receipt ledger | Compliance reporting |
| Framework-mapped report | Board report, ATO package |
Example: Healthcare AI Triage (HIPAA)
You: "Our clinical AI just triaged patient #4422 as ESI-3 with 67% confidence.
Sign this decision for HIPAA compliance."
Claude (via TrustAtom MCP):
✅ Receipt ta_7f3a2b signed in 1.2ms
Action: TRIAGE_PATIENT
Decision: ALLOW
Compliance: HIPAA:164.312(b), HL7
Risk Score: 0.80
Signature: ed25519:abc123...What the auditor sees: "On Mar 7 at 14:22, clinical-ai-v2 classified patient #4422 as ESI-3. Receipt ta_7f3a2b is Ed25519-signed. Control: HIPAA 164.312(b)."
Compliance Frameworks
TrustAtom auto-maps actions to framework controls:
Action | Frameworks |
| HIPAA 164.312(b), HL7 |
| SOX 302, FCRA |
| SOX 302, SEC 17a-4 |
| NIST PR, SOC2 CC6.1 |
| NIST PR/RS, SOC2 A1.2 |
Custom | NIST PR (default) |
Performance
Signing: <3ms average (Ed25519 + SHA-256)
Verification: <1ms
Receipt size: ~500 bytes JSON
Architecture
Your AI Agent
↓ (MCP call)
TrustAtom MCP Server (local)
├── Ed25519 key pair (you own the keys)
├── SHA-256 evidence hash
├── Compliance auto-mapping
└── In-memory ledger (pluggable to Neo4j/SQLite)
↓
Receipt returned to your agentEval Tests
8 tests covering signing, verification, tampering detection, compliance mapping, risk scoring, and performance:
npm test
# ✅ Signs a decision and returns a valid receipt
# ✅ Verifies an authentic receipt
# ✅ Detects tampered receipt
# ✅ Auto-maps TRIAGE_PATIENT to HIPAA compliance tags
# ✅ Auto-maps APPROVE_LOAN to SOX compliance tags
# ✅ Computes risk score from action when not provided
# ✅ Signs DENY decisions with same integrity
# ✅ Signs within 3ms target for production use
# Results: 8 passed, 0 failedEnterprise
Need hosted infrastructure with SLA? Contact hello@cyberwarriornetwork.com
Tier | Calls/day | Price |
Developer | 1,000 | Free |
Professional | 100,000 | $299/mo |
Enterprise | Unlimited | $2,499/mo |
Built By
Cyber Warrior Network — Trust Gate: Policy-gated AI decisions with cryptographic receipts.
No Receipt. No Trust.
Maintenance
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CWNApps/trustatom-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server