gamai-trust
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GAMAI_TRUST_DB | No | Set this to choose the antibody SQLite path. | |
| GAMAI_TRUST_ROOT | No | Set this if the component scripts live elsewhere than the checkout. The package loads the component scripts from the checkout by default. |
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 |
|---|---|
| trust_verify_claimsB | Fail-closed claim verification. Each claim has text, predicate, observed and expected. Returns confirmed/refuted/unverified and a SHA-256-bound report. |
| trust_check_injectionB | Check untrusted text for prompt injection using patterns and learned antibodies. Returns allow, attack_class, risk and reason. |
| trust_add_antibodyC | Store a blocked sample as an antibody signature (exact + near-miss). |
| trust_statsB | Antibody store statistics: total, active, dormant, expired, classes. |
| trust_demoB | Run the proofgate, immunity and crossnode demos. |
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 5 tools
Each tool targets a distinct action: verify claims, check for injection, add an antibody, view stats, or run demos. Minor potential confusion between trust_check_injection and trust_add_antibody since both concern the antibody system, but descriptions clarify the boundaries.
All tools share the trust_ prefix and mostly use verb_noun (verify_claims, check_injection, add_antibody). However, trust_stats and trust_demo use bare nouns rather than verb phrasing, a minor inconsistency.
Five tools is well-scoped for a trust/security server and each earns its place except trust_demo, which is a convenience/demo tool rather than core functionality.
The antibody lifecycle is incomplete: you can add an antibody and get aggregate stats, but there is no way to list, get, update, or delete individual antibodies. Core verification and injection checks are covered, but a management gap remains.