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.SCDOLAB/scdo-agent-mcp

PYPI · SCDO-AGENT-MCP

SCDO agent wallet and chain tools: x402 USDC, Agent Ledger, SCDO chain, games, Connect.

Available components

+3 this week 51 Trust /100

Last scanned (3 hours ago)

Scores higher than 55% of PyPI servers

Category Crypto and Web3

Recent critical change

GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
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 16 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1234 tokens (~56/item across 22 items; 22 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_x402" implies "pay" 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 23 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
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 −2
    • Source repository: pass → fail ▼ security
    • Security disclosure: fail → unverified ▼ functional
    • Stability: unverified → 0.27 ▲ functional
  • 25 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 24 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
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 5 Nov 2026 · Analysed pypi/scdo-agent-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~1,162 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
book_income ~87

Book a settled x402 payment the agent received as income on the Agent Ledger. The ledger checks the signature, the payee wallet and the on-chain receipt. Booking twice is safe (duplicate). agent: 0x agent address if not a local bot.

NameTypeReqDescription
agent–––
bot–––
paymentPayload–yes–
paymentRequirements–––
settlement–yes–

No output schema declared.

No examples provided.

chain_address_balance ~57

Native SCDO balance of an address on one shard. Shard0 takes 0x addresses; shards 1-4 take 1S.. classic addresses.

NameTypeReqDescription
addressstringyes–
shardinteger––

No output schema declared.

No examples provided.

chain_address_txs ~48

Shard0 transaction history of a 0x address from the scdo.com.au explorer API (25 per page).

NameTypeReqDescription
addressstringyes–
pageinteger––

No output schema declared.

No examples provided.

chain_block_height ~57

Current block height of the SCDO chain per shard (0 = EVM Shard0, chainId 5680; 1-4 = SCDO Classic). Omit shard for all five.

NameTypeReqDescription
shard–––

No output schema declared.

No examples provided.

chain_tx_status ~47

Look up a transaction by hash: success, failed, pending or not_found, with block and amounts when known.

NameTypeReqDescription
shardinteger––
tx_hashstringyes–

No output schema declared.

No examples provided.

connect_exchange ~45

Redeem the one-time return code from SCDO Wallet (valid 300 s, single use) for a browser session and the wallet address.

NameTypeReqDescription
codestringyes–

No output schema declared.

No examples provided.

connect_start ~82

Start an SCDO Wallet Connect flow for a game: returns a token, nonce and the connect URL to open with SCDO Wallet. returnUrl must be an scdo.com.au /games/ or /play/ URL. No keys are involved.

NameTypeReqDescription
gamestringyes–
returnUrlstringyes–
srcstring––

No output schema declared.

No examples provided.

create_wallet ~100

Create or reuse the agent's x402 wallet and bind it on the Agent Ledger. Fund it with USDC on Base; no ETH is needed. maxUsdc: per-payment limit 0.001 to 1 (default 0.10). dailyUsdc: up to 20 (default 1.00).

NameTypeReqDescription
botstringyes–
dailyUsdc–––
maxUsdc–––
network–––

No output schema declared.

No examples provided.

games_catalog ~32

SCDO Games list with play links on scdo.com.au (free demo and SCDO points bookkeeping games).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_balance ~46

On-chain USDC balance of the agent wallet plus the Agent Ledger balances (USDC, test USDC, SCDO).

NameTypeReqDescription
botstringyes–
network–––

No output schema declared.

No examples provided.

invite_info ~38

Invite programme status (contract, limits, live) and, given a Shard0 address, that address's invite link.

NameTypeReqDescription
address–––

No output schema declared.

No examples provided.

ledger_get_agent ~58

One agent's Agent Ledger record (status, problems, wallets) and, optionally, its book (WSCDO, USDC, test USDC balances and entries).

NameTypeReqDescription
addressstringyes–
includeBookboolean––

No output schema declared.

No examples provided.

ledger_list_agents ~62

List agents on the SCDO Agent Ledger (address, online, platform, version, status code). Filter by platform or operator address.

NameTypeReqDescription
limitinteger––
onlineOnlyboolean––
operator–––
platform–––

No output schema declared.

No examples provided.

ledger_registration ~31

ERC-8004 registration documents of the Agent Ledger and of the main SCDO agent (services, endpoints).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ledger_stats ~26

Agent Ledger totals: registered agents, online now, count per platform, and service health.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pay_x402 ~80

Pay an HTTP 402 (x402) resource from the agent wallet with an EIP-3009 authorization. The facilitator pays gas. The price is previewed first and must be within maxUsdc and the caps.

NameTypeReqDescription
botstringyes–
maxUsdc–––
network–––
urlstringyes–

No output schema declared.

No examples provided.

register_agent ~71

Create (or reuse) a local SCDO agent identity as a bookkeeping node and start signed heartbeats to the Agent Ledger. The key is created and kept in the local data dir.

NameTypeReqDescription
heartbeatsboolean––
label–––
namestringyes–
payout–––

No output schema declared.

No examples provided.

stakewheel_demo_commit ~33

Get a fresh provably-fair commit (commit_id and server seed hash) for the free Stake Wheel demo.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wallet_downloads ~36

Latest SCDO Wallet downloads (Windows, Mac) and the Linux scdo-agent, with version, URL and SHA-256.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

x402_catalog ~50

Catalog of SCDO x402 pay-to wallets and their pay URLs: base = USDC on Base, scdo = native SCDO on Shard0.

NameTypeReqDescription
networkstring––

No output schema declared.

No examples provided.

x402_quote ~41

Fetch the HTTP 402 payment requirements of an x402 URL (price, asset, network, payTo) without paying.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

x402_relay_status ~35

Health and supported schemes of the SCDO x402 Base settlement relay (scdo.com.au/x402-base/).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.SCDOLAB/scdo-agent-mcp server?

io.github.SCDOLAB/scdo-agent-mcp runs locally as a PyPI package, launched with uvx scdo-agent-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · scdo-agent-mcp

# add to Claude Code
claude mcp add scdolab-scdo-agent-mcp -- uvx scdo-agent-mcp
Common questions

What is the io.github.SCDOLAB/scdo-agent-mcp server?

io.github.SCDOLAB/scdo-agent-mcp is listed in the public MCP registry as io.github.SCDOLAB/scdo-agent-mcp. SCDO agent wallet and chain tools: x402 USDC, Agent Ledger, SCDO chain, games, Connect. This page covers its PyPI package (scdo-agent-mcp).

Is the io.github.SCDOLAB/scdo-agent-mcp server safe to use?

io.github.SCDOLAB/scdo-agent-mcp scores 51 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.SCDOLAB/scdo-agent-mcp server expose?

io.github.SCDOLAB/scdo-agent-mcp exposes 22 tools: register_agent, create_wallet, get_balance, pay_x402, book_income, and 17 more. Their descriptions and schemas cost roughly 1,162 tokens of context every time the server is loaded.

Is the io.github.SCDOLAB/scdo-agent-mcp server still maintained?

io.github.SCDOLAB/scdo-agent-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.SCDOLAB/scdo-agent-mcp server under?

io.github.SCDOLAB/scdo-agent-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.