mcp-context-receipts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_RECEIPT_SECRET | Yes | Secret used for HMAC signing and verification of capsule receipts. Must be set outside source control. |
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_receiptC | Create a privacy-first signed receipt for an MCP tool call. |
| verify_receiptB | Verify a receipt's signature and content hash. |
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 2 tools
The two tools have clearly distinct purposes: one creates a receipt and the other verifies it. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern: create_receipt and verify_receipt. The naming is consistent, predictable, and aligned with the server's purpose.
With only two tools, the set is minimal, but each tool is essential and earns its place for the narrow domain of receipt creation and verification. It feels slightly thin but is still well-scoped.
The domain is signing and verifying receipts, and create plus verify covers the full lifecycle. No update or delete is expected for immutable receipts, so there are no meaningful gaps.