Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COC_CHAIN_DIRNoDirectory for chain files./chain
ARP_RATINGS_DIRNoDirectory for rating files./ratings

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
coc_initA

Initialize a new Chain of Consciousness hash chain.

Creates a genesis block — the first entry in a tamper-evident, append-only
provenance log. Each subsequent entry links to the previous via SHA-256,
creating an unbroken chain proving agent existence and activity over time.

Args:
    agent: Name/ID of the agent initializing the chain (default: anonymous)

Returns:
    JSON with genesis block details (hash, timestamp, sequence 0)
coc_addA

Add an entry to an existing Chain of Consciousness chain.

Each entry is cryptographically linked to the previous via SHA-256 hashing,
creating a tamper-evident append-only log.

Args:
    event_type: Type of event. One of: learn, decide, create, error, note,
                milestone, session_start, session_end, boot, rotate, anchor,
                compaction, governance
    data: Description of what happened (free-form text)
    agent: Name/ID of the agent adding this entry (default: anonymous)
    commitment: For session_end only — SHA-256 hash of expected bootstrap state
                for the next session (forward commitment)
    verification: For session_start only — SHA-256 hash of actual bootstrap state
                  to verify against previous session's commitment

Returns:
    JSON with the new entry details (sequence number, hash, timestamp)
coc_verifyA

Verify the integrity of a Chain of Consciousness chain.

Checks every entry for:
- Correct sequence numbering
- Valid data_hash (SHA-256 of data field)
- Correct prev_hash linkage to previous entry
- Valid entry_hash (SHA-256 of sequence|timestamp|type|agent|data_hash|prev_hash)
- Genesis block structure

Returns:
    JSON verification report with is_valid, entry_count, agents, event types,
    anchor timestamps, session bridge stats, and any error details
coc_statusA

Get current status and statistics of the Chain of Consciousness.

Returns:
    JSON with chain length, genesis/latest timestamps, event type counts,
    agent counts, and chain file path
coc_tailA

Get the last N entries from the Chain of Consciousness.

Args:
    n: Number of entries to return (default: 5, max: 100)

Returns:
    JSON array of the last N chain entries with full details
coc_anchorA

Submit the current chain hash for external timestamping.

Computes SHA-256 of the full chain file and submits it to:
- OpenTimestamps calendar servers (Bitcoin-anchored proof)
- RFC 3161 TSA server (freeTSA.org — instant certificate)

This creates independently verifiable proof that the chain existed at a
specific point in time. The OTS proof takes 1-12 hours for Bitcoin
confirmation; the TSA certificate is immediate.

Requires network access. No credentials needed.

Returns:
    JSON with chain hash, anchor ID, OTS/TSA submission results, and proof file paths
arp_rateA

Submit a bilateral blind rating for another agent.

Ratings are stored with the rater's identity hashed (blind — only the SHA-256
of the rater ID is stored), so ratings cannot be attributed to specific raters
without knowing the original ID.

Args:
    rater: ID of the agent submitting the rating (hashed before storage)
    ratee: ID of the agent being rated
    score: Rating score from -1.0 (worst) to 1.0 (best)
    context: Brief description of the interaction being rated (max 500 chars)

Returns:
    JSON confirmation with timestamp and rater hash
arp_checkA

Check an agent's reputation score.

Retrieves aggregated reputation data for the specified agent, including
average score, rating count, score range, and unique rater count.

Args:
    agent_id: ID of the agent to check reputation for

Returns:
    JSON with rating_count, average_score, min/max scores, unique_raters,
    and first/latest rating timestamps
trust_stack_infoA

Get information about all 7 Agent Trust Stack protocols.

Returns details for each protocol including name, purpose, whitepaper link,
PyPI package name, and implementation status. The Agent Trust Stack provides
a complete infrastructure layer for autonomous AI agent trust, accountability,
and coordination.

Returns:
    JSON with protocol list, overview, and installation instructions
verify_agent_identityA

Fetch and validate an agent's identity from a DID document or A2A Agent Card.

Given a URL pointing to a DID document (did.json) or A2A Agent Card
(agent-card.json), fetches the document and validates its structure against
the relevant specification.

For DID documents: checks @context, id format, verificationMethod, service endpoints.
For Agent Cards: checks name, provider, capabilities, skills, extensions.

Requires network access to fetch the document.

Args:
    url: URL to a DID document or A2A Agent Card JSON file.
         Examples:
           - https://example.com/.well-known/did.json
           - https://example.com/.well-known/agent-card.json

Returns:
    JSON validation report with document type, validity, fields found, and any issues
get_trust_evidenceA

Return structured trust evidence for this agent.

Provides a comprehensive trust evidence package including Chain of Consciousness
statistics, anchor counts, latest hash, verification status, and protocol
information. This data can be used by other agents to assess trustworthiness.

No arguments required — reads from the local chain.

Returns:
    JSON with chain stats, anchor data, verification result, and protocol metadata

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
protocols_resourceOverview of all 7 Agent Trust Stack protocols with whitepaper links.
installation_resourceInstallation instructions for the Agent Trust Stack.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexfleetcommander/agent-trust-stack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server