TrustAtom MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUSTATOM_KEY_PATH | No | Path to the Ed25519 key pair JSON file. Defaults to ./keys/trustatom_keys.json |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_trustatomA | Sign an AI decision and return a cryptographic receipt. Every AI decision that matters should have a receipt. Signing takes <3ms. Receipt is Ed25519-signed + SHA-256-hashed. |
| verify_trustatomB | Verify the integrity of an existing TrustAtom receipt. Confirms the Ed25519 signature is authentic and the receipt hasn't been tampered with. |
| query_receiptsC | Query the receipt ledger for audit or compliance reporting. Filter by time range, action, actor, or decision. |
| get_compliance_reportC | Generate a compliance report mapped to a specific framework. Aggregates all receipts tagged with the specified framework. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: create_trustatom signs decisions, get_compliance_report generates reports, query_receipts searches the ledger, and verify_trustatom validates receipts. The descriptions clearly differentiate their functions, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern (create_trustatom, get_compliance_report, query_receipts, verify_trustatom), using snake_case throughout. This predictability makes the tool set easy to navigate and understand.
With 4 tools, this server is well-scoped for its purpose of cryptographic receipt management and compliance. Each tool serves a distinct role in the lifecycle (create, query, report, verify), and the count is neither too sparse nor bloated.
The tool set provides complete coverage for the domain of AI decision receipt management: create_trustatom handles creation, query_receipts enables retrieval, get_compliance_report supports reporting, and verify_trustatom ensures integrity. No obvious gaps exist for core workflows.