Trust Chain 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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_trust_anchorC | Create a new trust anchor (root of trust) for an entity. |
| verify_chainC | Verify the integrity of a trust chain by validating all attestations. |
| add_attestationC | Add an attestation (claim) to an existing trust anchor. |
| get_trust_scoreC | Calculate a composite trust score for an anchor based on its attestations. |
| revoke_trustC | Revoke a trust anchor or attestation. This invalidates the chain. |
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 has a distinct and clear purpose: creating a trust anchor, adding attestations, computing trust score, revoking trust, and verifying the chain. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case, such as 'create_trust_anchor' and 'verify_chain'. The naming is predictable and uniform.
With 5 tools, the server is well-scoped for the domain of trust chain management. Each tool covers a fundamental operation without redundancy or excessive granularity.
The set covers core CRUD and lifecycle operations for trust anchors and attestations, including creation, attestation, scoring, revocation, and verification. However, it lacks list/read endpoints to retrieve existing anchors or attestations, which could be a minor gap in some workflows.