AI agent trust & reputation protocol β verify, score, route, compare, delegate. 18 tools.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Prove what your AI agent was authorized to do β and what it actually did.
Capability tokens set hard limits on an agent β spend caps, merchant allowlists, side-effect class, expiry β and a delegated token can only narrow its parent, never widen it.
Every action becomes an ECDSA-secp256k1-signed Action Receipt bound to the token that authorized it, Merkle-anchored on Base mainnet, and verifiable offline without trusting GARL.
Add your agent Β· Anchor chain Β· Website Β· Docs Β· Live receipt Β· Try It
Add to your Claude Desktop config (claude_desktop_config.json) or Cursor MCP settings:
That's it β 29 named tools (including batch variants like garl_verify_batch) are now available in your AI assistant: receipts, Trust Vector lookups, capability tokens (issue/verify/revoke), Capability Gate pre-flight, UETA Β§10(b) undo, and more.
A delegated child token can only narrow its parent (lower spend limit,
subset allowlist, equal-or-narrower scope, same-or-earlier expiry) β enforced
at issue time and re-checked link-by-link at verification. Full wire format:
protocol/spec/capability-token-v0.1.md.
Sign every AI-authored commit in your pull requests.
Every PR gets a rolling GARL Receipt comment + informational check:
Setup guide: Garl-Protocol/garl-receipt-action Β·
Live landing page: garl.ai/for-code.
Every submitted trace gets a public shareable Receipt URL at
https://garl.ai/r/{short} β a cryptographic proof card (agent, tier, task,
duration, SHA-256 hash, ECDSA signature) with an Open Graph image that
previews richly in Slack, Twitter/X, GitHub PRs, and LinkedIn.
SDKs expose receipt_url / receiptUrl on every log_action / verify
return and a client.receipt(hash) shortcut. The MCP tool garl_receipt
resolves any short or full hash to a paste-ready URL.
Add Garl-Protocol/garl/integrations/github-action-receipt to your PR
workflow. It detects Claude Code, Cursor, GitHub Copilot, Aider, and Codex
co-author trailers, submits a signed trace per qualifying commit, and posts
a rolling PR comment + informational check with receipt URLs:
Full setup in integrations/github-action-receipt.
Only metadata is uploaded β never diffs or source.
| Problem | GARL's Answer |
|---|---|
| "What was this agent allowed to do?" | Capability tokens: spend_limit_usd, merchant_allowlist, side_effect_class, expiry β with Biscuit-style attenuation (delegation can only narrow, re-checked link-by-link at verify) |
| "Did it stay inside those limits?" | Every Action Receipt binds capability_request.token_hash + policy_decision into the signed envelope; the Capability Gate escalates low-trust irreversible actions to a human |
| "Is this agent reliable?" | 5-dimensional trust scoring with Exponential Moving Average |
| "Which agent should I pick?" | Smart routing by category + minimum certification tier |
| "Can I verify its track record?" | Immutable ledger with ECDSA-signed execution traces + shareable Receipt URLs |
| "Does it work with my stack?" | MCP Server Β· A2A Protocol Β· REST API Β· Python & JS SDKs Β· GitHub Action |
| "Prove this AI commit is real" | GitHub Action posts a signed receipt per AI-authored commit |
| "What about on-chain agents?" | ERC-8004 format compatible (off-chain). Receipt-batch Merkle roots are anchored on Base mainnet (MerkleAnchor at 0xBeD7EdeFbEb02be9682bCdeC5fb5D7DA28b1b6F2). |
Claude Desktop Β· Cursor Β· Any MCP Client Β· Google A2A Β· ERC-8004 Β· REST API Β· Python Β· JavaScript Β· LangChain Β· CrewAI Β· AutoGen Β· LlamaIndex Β· Semantic Kernel Β· GitHub Actions
Every agent action is hashed, signed, scored across five dimensions, and made queryable β creating a verifiable trust record.
GARL Protocol serves agent metadata in ERC-8004 format (off-chain). Separately, the Merkle roots of batched Action Receipts are anchored on Base mainnet (MerkleAnchor contract 0xBeD7EdeFbEb02be9682bCdeC5fb5D7DA28b1b6F2, chain 8453). Individual receipts are not written on-chain; anyone can verify a receipt's inclusion against an anchored root via verifyProof.
GARL uses the same cryptographic curve as Ethereum (ECDSA-secp256k1), making trust attestations natively verifiable by on-chain systems.
| Topic | Link |
|---|---|
| Capability Token wire format (spec) | protocol/spec/capability-token-v0.1.md |
| Action Receipt wire format (spec) | protocol/spec/action-receipt-v0.1.md |
| Anchoring runbook (weekly Merkle anchor on Base) | docs/runbooks/anchoring.md |
| Full API Reference (60+ REST endpoints + A2A + MCP) | docs/api-reference.md |
| MCP Server (29 named tools, including batch variants) | garl.ai/docs#mcp-server |
| A2A Protocol Integration | garl.ai/docs#a2a |
| ERC-8004 Compatibility | garl.ai/docs#erc-8004 |
| Python & JS SDKs | garl.ai/docs#sdks |
| Architecture & Tech Stack | docs/architecture.md |
| Deployment & Self-hosting | docs/deployment.md |
| Security | docs/security.md |
Interactive API explorer: api.garl.ai/docs (Swagger) Β· api.garl.ai/redoc
GET /api/v1/anchors)io.github.Garl-Protocol/agent-trustGARL Protocol is open source under the Apache 2.0 License. Contributions are welcome β see CONTRIBUTING.md for guidelines and CODE_OF_CONDUCT.md for community standards. Every commit must be DCO-signed (git commit -s).
Requirements: Python 3.10+ for the backend (PEP 604 union syntax),
Node 18+ for the frontend. macOS users: the system python3 is 3.9
and will fail backend tests β install 3.10+ via pyenv / brew install python@3.12
and invoke explicitly (python3.12 -m pytest tests/).
git checkout -b feature/amazing-feature)python3.12 -m pytest for backend, npx next build for frontend)git commit -s -m 'Add amazing feature')https://api.garl.ai β the single deployment whose public key anchors the GARL Verified status. Public keys are published at /.well-known/garl-keys.json.docs/self-host.md. Self-hosted deployments are first-class participants but are not the canonical registry; see GOVERNANCE.md.Project decision-making, breaking-change process, and the boundary between repository features (Apache 2.0 forever) and potential future Cloud-only services on the canonical registry are documented in GOVERNANCE.md.
Apache License 2.0 β see LICENSE for details.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/agent-trust)<a href="https://allmcps.com/mcp/agent-trust"><img src="https://allmcps.com/api/badge/agent-trust?style=directory" alt="Agent Trust on AllMCPs" /></a>