attested
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATTESTED_BIN | No | Override the path to the attested CLI binary. By default the server runs the attested CLI bundled with it; this is the only override. |
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 |
|---|---|
| attested_runA | Use instead of screenshots to show that a change works. Run the test command through |
| attested_packetA | Return the failure packet from the last red |
| attested_statusA | Return the signed verdict for the project's attested/ctrf.json, built only from the Sigstore attestation that |
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 action and artifact: status returns the signed verdict, run executes tests and writes a receipt, and packet returns the failure packet from the last red run. Although status and packet both expose run-related information, their boundaries are clear and documented.
All three tools follow the same attested_<noun> convention, with short, predictable names. The pattern is consistent throughout and easy for an agent to remember.
Three tools are well scoped for a narrow attestation/receipt workflow: execute, inspect verdict, and retrieve failures. No tool appears redundant or out of place.
The core lifecycle is covered: run tests, read the signed verdict, and retrieve failure evidence. Minor gaps exist around configuration or receipt inspection, but the essential workflow has no obvious dead ends.