Agent Trust Stack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COC_CHAIN_DIR | No | Directory for chain files | ./chain |
| ARP_RATINGS_DIR | No | Directory for rating files | ./ratings |
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 |
|---|---|
| coc_initA | Initialize a new Chain of Consciousness hash chain. |
| coc_addA | Add an entry to an existing Chain of Consciousness chain. |
| coc_verifyA | Verify the integrity of a Chain of Consciousness chain. |
| coc_statusA | Get current status and statistics of the Chain of Consciousness. |
| coc_tailA | Get the last N entries from the Chain of Consciousness. |
| coc_anchorA | Submit the current chain hash for external timestamping. |
| arp_rateA | Submit a bilateral blind rating for another agent. |
| arp_checkA | Check an agent's reputation score. |
| trust_stack_infoA | Get information about all 7 Agent Trust Stack protocols. |
| verify_agent_identityA | Fetch and validate an agent's identity from a DID document or A2A Agent Card. |
| get_trust_evidenceA | Return structured trust evidence for this agent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| protocols_resource | Overview of all 7 Agent Trust Stack protocols with whitepaper links. |
| installation_resource | Installation instructions for the Agent Trust Stack. |
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes, especially the coc_* lifecycle actions (init, add, status, tail, verify, anchor) and arp_rate/arp_check. Minor overlap exists between get_trust_evidence and coc_status/coc_verify since both surface chain and verification data, but the intended use cases differ enough to avoid real confusion.
The coc_* and arp_* prefixes create useful grouping agenda, but naming style is mixed: some tools are prefix+verb (coc_add, arp_rate), some are prefix+noun (coc_status, coc_tail), and others use generic verb/noun patterns (get_trust_evidence, verify_agent_identity, trust_stack_info). The conventions are readable but not fully consistent.
Eleven tools is an appropriate size for a trust-stack server covering chain-of-consciousness, reputation, and identity verification. Each tool provides a distinct operation, and the count feels neither bloated nor overly minimal.
The core workflows are well covered: chain initialization, appending, tail inspection, verification, anchoring, reputation rating/checking, identity validation, and local trust evidence retrieval. Minor gaps exist, such as no per-entry chain lookup or richer reputation aggregation, but these are workable for the domain.