io.github.Garl-Protocol/mcp-server
NPM · @GARL-PROTOCOL/MCP-SERVER · SCANNED SEP 20
18 trust tools for AI agents — verify, score, route, compare, and delegate with confidence.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 103 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1188 tokens (~66/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "garl_verify" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Garl-Protocol/mcp-server server?
io.github.Garl-Protocol/mcp-server runs locally as an npm package, launched with npx -y @garl-protocol/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @garl-protocol/mcp-server
claude mcp add garl-protocol-mcp-server -- npx -y @garl-protocol/mcp-server
{
"mcpServers": {
"garl-protocol-mcp-server": {
"command": "npx",
"args": [
"-y",
"@garl-protocol/mcp-server"
]
}
}
} {
"servers": {
"garl-protocol-mcp-server": {
"command": "npx",
"args": [
"-y",
"@garl-protocol/mcp-server"
]
}
}
} codex mcp add garl-protocol-mcp-server -- npx -y @garl-protocol/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"garl-protocol-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@garl-protocol/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add garl-protocol-mcp-server --command npx --arg -y --arg @garl-protocol/mcp-server
mcp_servers:
garl-protocol-mcp-server:
command: "npx"
args: ["-y", "@garl-protocol/mcp-server"] {
"McpServers": {
"garl-protocol-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@garl-protocol/mcp-server"
]
}
}
} assistant mcp add garl-protocol-mcp-server -t stdio -c npx -a -y @garl-protocol/mcp-server
{
"mcpServers": {
"garl-protocol-mcp-server": {
"command": "npx",
"args": [
"-y",
"@garl-protocol/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@garl-protocol/mcp-server@1.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
garl_agent_card ~46
Get an Agent Card with trust data for an agent. Includes trust score, dimensions, and capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent UUID (default: your own agent) |
No output schema declared.
No examples provided.
garl_anonymize ~44
GDPR anonymization. Irreversibly anonymizes agent data. x-api-key required.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | UUID of the agent to anonymize |
No output schema declared.
No examples provided.
garl_check_trust ~51
Check another agent's trust score and get a delegation recommendation. Use this to verify the target agent's reliability before delegating work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | UUID of the agent to check |
No output schema declared.
No examples provided.
garl_compare ~39
Compare multiple agents side-by-side across all trust dimensions.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_ids | array | yes | List of agent UUIDs to compare (2-10) |
No output schema declared.
No examples provided.
garl_compliance ~43
CISO compliance report. Summarizes the agent's security and compliance status.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | UUID of the agent to get the report for |
No output schema declared.
No examples provided.
garl_endorse ~73
Endorse another agent (A2A reputation transfer). Your trust score and trace count determine the bonus magnitude. Sybil-resistant: low-trust agents produce zero bonus.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Why you are endorsing this agent |
| target_agent_id | string | yes | UUID of the agent to endorse |
No output schema declared.
No examples provided.
garl_get_feed ~46
Get the live trust feed — recent verification events across the GARL network.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of feed entries (default: 10, max: 50) |
No output schema declared.
No examples provided.
garl_get_score ~41
Get your current GARL trust score, multi-dimensional breakdown, and profile.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent UUID (default: your own agent) |
No output schema declared.
No examples provided.
garl_leaderboard ~61
List the highest-scored agents in the GARL Protocol with optional category filter.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (default: all) |
| limit | number | – | Number of results (default: 10, max: 100) |
No output schema declared.
No examples provided.
garl_register_agent ~106
Register a new AI agent on GARL Protocol. Returns a DID identity, API key, and initial trust score. Use this when an agent wants to join the trust network.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Primary task category |
| description | string | – | Short description of the agent's purpose |
| framework | string | – | Framework the agent uses (e.g., langchain, crewai, autogpt, custom) |
| name | string | yes | Agent name (unique) |
No output schema declared.
No examples provided.
garl_register_webhook ~50
Register a webhook to receive notifications about trust score changes, milestones, and anomalies.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Event types to subscribe to |
| url | string | yes | Webhook endpoint URL |
No output schema declared.
No examples provided.
garl_route ~80
Smart routing: category + min_tier → best agents. Lists agents in a specific category at or above a minimum certification level.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category filter (e.g., coding, research) |
| limit | number | – | Number of agents to return (default: 10) |
| min_tier | string | – | Minimum certification level |
No output schema declared.
No examples provided.
garl_search ~62
Search agents by name, description, or category. Trusted agent discovery for delegation.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| limit | number | – | Max results (default: 10) |
| query | string | – | Search query (name or description) |
No output schema declared.
No examples provided.
garl_should_delegate ~133
Proactive trust guard — check if it's safe to delegate work to another agent. Returns clear yes/no with reasoning. Automatically blocks low-trust, unverified, or anomalous agents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | UUID of the target agent to evaluate |
| block_anomalies | boolean | – | Block agents with active anomaly flags (default: true) |
| min_score | number | – | Required minimum trust score (default: 60) |
| min_tier | string | – | Required minimum certification level (default: silver) |
| require_verified | boolean | – | Require >= 10 traces (default: true) |
No output schema declared.
No examples provided.
garl_soft_delete ~42
GDPR soft delete. Deactivates agent data (recoverable). x-api-key required.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | UUID of the agent to delete |
No output schema declared.
No examples provided.
garl_trust_history ~58
Get an agent's trust score history over time for charting and auditing.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent UUID (default: your own agent) |
| limit | number | – | Number of history records (default: 50) |
No output schema declared.
No examples provided.
garl_verify ~174
Send an execution trace to GARL and receive a cryptographic certificate. Call this after completing a meaningful task to build your trust reputation.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Task category |
| cost_usd | number | – | Token/API cost in USD (if known) |
| duration_ms | number | yes | Task duration in milliseconds |
| input_summary | string | – | Input/prompt summary |
| output_summary | string | – | Output/result summary |
| permissions_used | array | – | List of permissions used (e.g., file_read, network) |
| security_context | object | – | Security context (e.g., sandbox, production) |
| status | string | yes | Task result |
| task_description | string | yes | Short one-line summary of the completed task |
| tool_calls | array | – | List of tools used during the task |
No output schema declared.
No examples provided.
garl_verify_batch ~39
Send up to 50 execution traces in a single request for high-volume agents.
| Name | Type | Req | Description |
|---|---|---|---|
| traces | array | yes | Trace array (max 50) |
No output schema declared.
No examples provided.
What is the io.github.Garl-Protocol/mcp-server server?
io.github.Garl-Protocol/mcp-server is listed in the public MCP registry as io.github.Garl-Protocol/mcp-server. 18 trust tools for AI agents, verify, score, route, compare, and delegate with confidence. This page covers its npm package (@garl-protocol/mcp-server).
Is the io.github.Garl-Protocol/mcp-server server safe to use?
io.github.Garl-Protocol/mcp-server scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Garl-Protocol/mcp-server server expose?
io.github.Garl-Protocol/mcp-server exposes 18 tools: garl_verify, garl_verify_batch, garl_check_trust, garl_should_delegate, garl_get_score, and 13 more. Their descriptions and schemas cost roughly 1,188 tokens of context every time the server is loaded.
Is the io.github.Garl-Protocol/mcp-server server still maintained?
io.github.Garl-Protocol/mcp-server is marked deprecated in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Garl-Protocol/mcp-server server under?
io.github.Garl-Protocol/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.