# @garl-protocol/mcp-server

GARL Protocol MCP Server — cryptographic verification for AI agent actions. 29 named tools: submit signed Action Receipts (v0.1), query multi-dimensional Trust Vector, issue/verify/revoke capability tokens (JWT-shaped + ECDSA-secp256k1), Capability Gate p

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.4.3
- **Author:** garl-protocol
- **License:** Apache-2.0
- **npm:** @garl-protocol/mcp-server
- **Source:** https://github.com/Garl-Protocol/garl
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 11 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-17T11:37:30.764Z
- **Version scanned:** 1.4.3
- **CVEs:** none found by OSV at scan time

## Tools

29 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `garl_verify`
- `garl_verify_batch`
- `garl_check_trust`
- `garl_should_delegate`
- `garl_get_score`
- `garl_trust_history`
- `garl_leaderboard`
- `garl_compare`
- `garl_agent_card`
- `garl_endorse`
- `garl_register_webhook`
- `garl_search`
- `garl_route`
- `garl_compliance`
- `garl_register_agent`
- `garl_get_feed`
- `garl_soft_delete`
- `garl_anonymize`
- `garl_trust_gate`
- `garl_receipt`
- `garl_simulate_score`
- `garl_get_trust_vector`
- `garl_record_action_receipt`
- `garl_issue_capability_token`
- `garl_verify_capability_token`
- `garl_revoke_capability_token`
- `garl_evaluate_action`
- `garl_undo_action`
- `garl_get_anchor_proof`

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@garl-protocol/mcp-server\"\n      ],\n      \"env\": {\n        \"GARL_API_KEY\": \"<YOUR_GARL_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `GARL_API_KEY` — Garl API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 52, ceiling 52 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40garl-protocol%2Fmcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40garl-protocol%2Fmcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40garl-protocol%2Fmcp-server
- HTML page: https://forgeregistry.com/registry/%40garl-protocol%2Fmcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.