tremelay-mcp
OfficialServer 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| describe_capabilityC | Describe one exact credential-use capability by handle. |
| invoke_capabilityA | Invoke the exact capability named by handle. http_request accepts only handle; http_broker takes method and path, plus optional query, headers and body_base64, all under the handle's granted origin and prefix; attestation requires a base64 payload; SSH requires one unframed base64 SSH-agent message (1–4096 bytes) after host session binding. Never replay an ambiguous or cancelled invocation. |
| list_capabilitiesB | List this endpoint's exact credential-use capabilities. |
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 split cleanly along list/describe/invoke lines, and each targets a distinct operation on a capability handle. describe_capability and list_capabilities are adjacent in purpose but their singular-vs-collection scope keeps them separable.
All three follow a consistent verb_noun snake_case pattern (list_capabilities, describe_capability, invoke_capability). The only blemish is the singular/plural mismatch between 'capability' and 'capabilities', a minor cosmetic deviation.
Three tools is a lean but coherent minimal triad for a credential-use broker: enumerate, inspect, execute. Nothing feels redundant, though the surface is on the thin side given invoke_capability absorbs several distinct invocation modes (http_request, http_broker, attestation, SSH).
Discovery and invocation are covered, but the domain implies lifecycle operations that are absent. The warning about 'ambiguous or cancelled invocation' suggests cancellation/status exists conceptually yet no tool exposes it, leaving a notable gap.