Canari
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANARI_STORE | No | Path to a full ledger checkout (alternative to the --store flag). When set, the complete supersession history is used instead of the bundled snapshot. No arguments are required; the wheel ships a snapshot of the newest signed attestation per component. |
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 |
|---|---|
| gate_checkB | Look up a component (registry+name[,version]) in the signed attestation ledger and return the install-gate decision (ALLOW/BLOCK/REVIEW) with reasons. |
| verify_bundleB | Offline verification of one canari bundle: DSSE/Ed25519 signature + schema + per-check breakdown. |
| store_summaryC | Coverage summary of the local ledger store plus the latest drift headline (verdict flips / silent changes). |
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 targets a clearly distinct operation: gate decision lookup, offline bundle verification, and ledger/store summary. The descriptions make the boundaries explicit, so an agent should not confuse them.
All names use lowercase snake_case with two tokens, which is consistent and readable. However, the semantic pattern is not uniformly verb_noun: verify_bundle is clearly verb_object, while gate_check and store_summary read more like noun phrases.
Three tools are appropriate for a focused attestation/verification server. Each tool has a distinct role and earns its place without bloating the surface.
The core read/verification workflows are covered: gate decisions, bundle verification, and ledger coverage/drift summary. Minor gaps remain around inspecting raw attestation entries or detailed component history beyond the decision headline.