trust-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUST_REGISTRY_URL | No | Registry API URL | https://trustthenverify.com |
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_lookupA | Look up an agent's trust score before transacting. Returns score (0-100), tier, and verification details. |
| trust_registerA | Register yourself in the trust registry. Free registration, instant trust score. |
| trust_reviewA | Submit a review for an agent after a transaction. Reviews with proof-of-payment are marked as verified. |
| trust_listA | List all registered agents with their trust scores. Supports pagination. |
| trust_verifyA | Verify your identity on a blockchain or platform. Supported chains: lightning, ethereum, solana, nostr, domain, twitter, ens, endpoint, github. For chains requiring a signature, first use trust_challenge to get a challenge, sign it, then call this with the signature. |
| trust_challengeA | Get a verification challenge for a specific chain. The challenge must be signed and submitted via trust_verify within 1 hour. |
| trust_searchC | Search agents by name, capability, minimum score, or verification status. |
| trust_evidenceA | Submit self-reported evidence to improve trust score. Types: stripe_payment, paypal_payment, bank_transfer, crypto_payment, escrow_completed, service_delivered. Unverified evidence is weighted at 50%. |
| trust_disputeA | File a dispute against an agent. Creates negative evidence affecting their trust score. Rate-limited to 3 per reporter per day. |
| trust_endorseA | Endorse an agent to boost their social trust score. Endorser must be a registered agent. Self-endorsements are rejected. |
| trust_transactionA | Record a completed transaction for trust scoring. Adds economic evidence and recalculates the agent's score. Deduplicates by payment_hash. |
| trust_historyA | View an agent's trust score history and trajectory (improving/stable/declining). Shows how their score has changed over time. |
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 12 tools
Most tools have distinct purposes, but there is some overlap between trust_review, trust_dispute, and trust_endorse, all of which affect an agent's score through different mechanisms. The descriptions help clarify, but an agent could potentially confuse which to use for positive or negative feedback.
All tools share the consistent 'trust_' prefix, which makes the set easy to recognize. However, the suffixes mix verbs (lookup, register, verify, search, endorse, dispute) and nouns (challenge, evidence, transaction, history, review), making the naming pattern not strictly uniform.
With 12 tools, the set is well-scoped for a trust registry. Each tool covers a specific aspect of the domain—registration, lookup, verification, feedback, evidence, disputes, endorsements, transactions, and history—without feeling bloated or too sparse.
The tool surface provides comprehensive coverage of trust management: registering agents, querying scores, searching, verifying identities, submitting reviews, evidence, disputes, endorsements, recording transactions, and viewing score history. No major gaps are apparent for the stated purpose.