sdcreceipt-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEY | Yes | Path to the signing key (PEM file) used for sign_trigger | |
| TOKEN | No | Token for the settle endpoint (required to enable the settle tool) | |
| KEY_ID | Yes | Key ID URI for the signing key | |
| ENDPOINT | No | Endpoint URL for settle (required to enable the settle tool) |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_receiptA | Verify a VSL Settlement Receipt. Runs every check and reports all of them, including the ones that passed, rather than stopping at the first failure. Requires no network and no account: the issuer key document is supplied by the caller. Use this to decide whether a Receipt you were sent is trustworthy before acting on it. |
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 1 tool
With only a single tool, there is no possibility of confusing it with another tool. Its purpose (verify a VSL Settlement Receipt) is stated clearly and unambiguously.
The lone tool follows a clean verb_noun snake_case convention (verify_receipt), which is the idiomatic form for MCP tools. No naming conflicts or mixed conventions exist.
A single tool is thin even for a narrow domain; there is no way to run individual checks, fetch issuer keys, or introspect the verification process. It is defensible for a focused verifier but leaves no granularity for callers.
The tool covers the core lifecycle of the stated purpose (full verification reporting all checks, including passes), so the main workflow has no dead end. Minor gaps remain, such as discovering issuer keys or running a subset of checks, but the caller-supplied key document mitigates the biggest one.