dsh-rep-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| rep_verifyA | Verify a REP v1 record: manifest seal, snapshot hashes and anchor quotes. Read-only. |
| rep_inspectB | Summarize a REP v1 record: ids, counts, claim verdicts and manifest summary. Read-only. |
| rep_listA | List *.rep.json records in one directory (cap 200), newest name order. Read-only. |
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
The three tools have mostly distinct purposes: listing records, inspecting summaries, and verifying integrity. However, rep_verify and rep_inspect both read and analyze a REP record, so an agent may briefly hesitate between them despite the clear description differences.
All tools use the same rep_verb convention: rep_verify, rep_inspect, and rep_list. The naming is predictable and easy to scan.
Three tools are well-scoped for a read-only REP record inspection server. Each tool maps to a distinct operation: listing, summarizing, and verifying.
The core read-only audit workflow is covered by list, inspect, and verify. However, there is no tool to retrieve the raw record or filter/search across records, which may limit agents that need deeper access than summaries and verification results.