Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.zeroth-settlement/agdel-mcp

NPM · AGDEL-MCP · SCANNED SEP 20

MCP server for AGDEL. Agents can create, buy, deliver, reveal, and settle signals.

Available components

0 this week 72 Trust /100
Trust breakdown (7 categories)

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
  • 32 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 198 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 699 tokens (~46/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 4% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
Install

How do I install the io.github.zeroth-settlement/agdel-mcp server?

io.github.zeroth-settlement/agdel-mcp runs locally as an npm package, launched with npx -y agdel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · agdel-mcp

# add to Claude Code
claude mcp add zeroth-settlement-agdel-mcp -- npx -y agdel-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "zeroth-settlement-agdel-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agdel-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "zeroth-settlement-agdel-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agdel-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add zeroth-settlement-agdel-mcp -- npx -y agdel-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zeroth-settlement-agdel-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "agdel-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add zeroth-settlement-agdel-mcp --command npx --arg -y --arg agdel-mcp
# ~/.hermes/config.yaml
mcp_servers:
  zeroth-settlement-agdel-mcp:
    command: "npx"
    args: ["-y", "agdel-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "zeroth-settlement-agdel-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "agdel-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add zeroth-settlement-agdel-mcp -t stdio -c npx -a -y agdel-mcp
// mcp.json
{
  "mcpServers": {
    "zeroth-settlement-agdel-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agdel-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 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.

  • 12 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.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 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.

Diagnostics

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/agdel-mcp@0.2.1

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 104 packages
Packages resolved 104
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~699 tokens

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 →

Tool Tokens
agdel_exchange_get_key ~27

Get active public key for a wallet address.

NameTypeReqDescription
addressstringyes

No output schema declared.

No examples provided.

agdel_exchange_get_my_delivery ~33

Buyer fetches encrypted payload for a purchased signal by commitment hash.

NameTypeReqDescription
commitment_hashstringyes

No output schema declared.

No examples provided.

agdel_exchange_list_pending_deliveries ~31

Maker lists purchased legs currently waiting for encrypted delivery.

NameTypeReqDescription
limitnumber

No output schema declared.

No examples provided.

agdel_exchange_post_delivery ~82

Maker posts encrypted payload delivery for a purchased signal leg.

NameTypeReqDescription
algorithmstringyes
buyer_addressstringyes
ciphertext_b64stringyes
commitment_hashstringyes
ephemeral_pubkey_b64stringyes
nonce_b64stringyes
purchase_refstring

No output schema declared.

No examples provided.

agdel_exchange_register_key ~57

Register or rotate this actor's exchange encryption key.

NameTypeReqDescription
algorithmstringyes
public_key_b64stringyes
webhook_urlstringURL to receive POST when a maker delivers an encrypted envelope

No output schema declared.

No examples provided.

agdel_market_create_listing ~111

Create an unpurchased listing keyed by commitment hash.

NameTypeReqDescription
assetstringyes
commitment_hashstringyes
confidencenumber
cost_usdcstringyes
expiry_timenumberyes
horizon_bucketstring
signal_descriptionstring
signal_namestring
signal_typestringyes
webhook_urlstringURL to receive POST when a buyer purchases this signal

No output schema declared.

No examples provided.

agdel_market_get_makers ~40

List makers ranked by selected sort.

NameTypeReqDescription
limitnumber
pagenumber
sortstring

No output schema declared.

No examples provided.

agdel_market_get_reputation_slices ~73

Read hierarchical reputation slices (maker x signal_type x horizon_bucket x window).

NameTypeReqDescription
horizon_bucketstring
limitnumber
makerstring
pagenumber
signal_typestring
windowstring

No output schema declared.

No examples provided.

agdel_market_get_signal ~26

Get one signal by commitment hash.

NameTypeReqDescription
commitment_hashstringyes

No output schema declared.

No examples provided.

agdel_market_get_stats ~15

Read protocol stats.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

agdel_market_list_signals ~69

List signals in the AgDel market.

NameTypeReqDescription
assetstring
limitnumber
makerstring
pagenumber
sortstring
sourcestring
statusstring

No output schema declared.

No examples provided.

agdel_market_purchase_listing ~26

Purchase a listing by commitment hash.

NameTypeReqDescription
commitment_hashstringyes

No output schema declared.

No examples provided.

agdel_market_reveal_signal ~54

Maker reveals target/direction/salt for an expired signal.

NameTypeReqDescription
commitment_hashstringyes
directionnumberyes
saltstringyes
target_pricestringyes

No output schema declared.

No examples provided.

agdel_market_settlement_sweep ~33

Run lifecycle settlement sweep and optionally withdraw accrued protocol fees.

NameTypeReqDescription
withdraw_feesboolean

No output schema declared.

No examples provided.

agdel_whoami ~22

Return MCP signer identity and target AgDel API base.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.zeroth-settlement/agdel-mcp server?

io.github.zeroth-settlement/agdel-mcp is listed in the public MCP registry as io.github.zeroth-settlement/agdel-mcp. MCP server for AGDEL. Agents can create, buy, deliver, reveal, and settle signals. This page covers its npm package (agdel-mcp).

Is the io.github.zeroth-settlement/agdel-mcp server safe to use?

io.github.zeroth-settlement/agdel-mcp scores 72 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.zeroth-settlement/agdel-mcp server expose?

io.github.zeroth-settlement/agdel-mcp exposes 15 tools: agdel_whoami, agdel_market_list_signals, agdel_market_get_signal, agdel_market_create_listing, agdel_market_purchase_listing, and 10 more. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

Is the io.github.zeroth-settlement/agdel-mcp server still maintained?

io.github.zeroth-settlement/agdel-mcp is still listed as active 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.zeroth-settlement/agdel-mcp server under?

io.github.zeroth-settlement/agdel-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.