actionproof
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACTIONPROOF_KEY_PATH | No | Override path for the agent's Ed25519 key file (default: ~/.actionproof/agent.key.pem) |
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 |
|---|---|
| attest_actionA | Create a signed, tamper-evident receipt that THIS agent performed an action (e.g. sent an email, filed a form, made a payment). Call it right after you perform the action. Returns a SignedReceipt you can store or share; anyone can later verify it offline. |
| verify_receiptA | Verify a signed ActionProof receipt offline. Returns whether the signature is valid and which agent did:key signed it. Optionally re-check that supplied params/result match the hashes in the receipt. |
| get_identityA | Return this ActionProof server's stable agent identity (a did:key). Receipts from attest_action are signed by this identity. |
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 3 tools
Each tool has a distinct purpose: attest_action creates a receipt, get_identity provides the signer's DID, and verify_receipt validates receipts. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: attest_action, get_identity, verify_receipt.
With only 3 tools, the server is minimal but well-scoped for its purpose. A few additional tools (e.g., list_receipts) could be useful but are not necessary.
The core workflow of attestation is fully covered: identity retrieval, action attestation, and receipt verification. No obvious gaps in the domain.