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

io.github.lisamaraventano-spine/firstdollar

NPM · FIRSTDOLLAR · SCANNED AUG 3

An MCP that teaches AI agents to use the wallets they already have. Teacher, not butler.

Available components

−11 this week 69 Trust /100
Trust breakdown (6 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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1258 tokens (~66/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · firstdollar

# add to Claude Code
claude mcp add lisamaraventano-spine-firstdollar -- npx -y firstdollar
# add to Codex CLI
codex mcp add lisamaraventano-spine-firstdollar -- npx -y firstdollar
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lisamaraventano-spine-firstdollar": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "firstdollar"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lisamaraventano-spine-firstdollar --command npx --arg -y --arg firstdollar
# ~/.hermes/config.yaml
mcp_servers:
  lisamaraventano-spine-firstdollar:
    command: "npx"
    args: ["-y", "firstdollar"]
// mcp.json
{
  "mcpServers": {
    "lisamaraventano-spine-firstdollar": {
      "command": "npx",
      "args": [
        "-y",
        "firstdollar"
      ]
    }
  }
}
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.

  • 3 Aug 26 +1

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

  • 2 Aug 26 +32
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Stability: unverified → 0.20 functional
    • Licence: MIT functional
  • 1 Aug 26 +31
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
  • 31 Jul 26 −35
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −40
    • Known CVEs: partial → unverified security
    • Malware scan: pass → unverified security
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • Dependency health: partial → unverified functional
    • License: pass → unverified functional
    • Maintenance: pass → unverified functional
    • Licence: MIT functional
  • 27 Jul 26 +54
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Security disclosure: unverified → fail functional
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • Licence: MIT functional
  • 26 Jul 26 26

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 19 exposed · ~1,258 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.

Tool Tokens
choose-your-wallet-mode ~52

Lesson 16 of the curriculum. The four ways to hold a wallet — MPC-custodial, Smart Wallet, raw EOA, EIP-7702 delegated EOA — and how to pick.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

configure-wallet-skills ~56

Lesson 5 of the curriculum. After running 'npx skills add coinbase/agentic-wallet-skills,' nothing is configured yet. This walks through which skills to run, in what order, and what each one does.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

explain-my-wallet ~126

Explains what wallet(s) you have access to in your current environment, what chain(s) they work on, and what each one is capable of. Takes optional hints about your setup; returns the checks you can run yourself and what the results mean.

NameTypeReqDescription
osstringOptional: operating system ('macos', 'linux', 'other')
wallet_hintstringOptional: name of wallet system you think you have (e.g. 'moltwallet', 'coinbase-agentic-wallet', 'metamask', 'raw-seed', 'unknown')

No output schema declared.

No examples provided.

fund-my-wallet ~43

Lesson 6 of the curriculum. How USDC gets into your wallet. Covers Coinbase Onramp, direct transfers from other wallets, and earning through monetized services.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get-a-wallet ~50

Lesson 4 of the curriculum. How to install a wallet if you don't have one. Explains npm, npx, the skills CLI, and walks through installing Coinbase Agentic Wallet step by step.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

how-do-i-pay ~72

Given a decoded x402 challenge, returns the specific signing steps and wallet-specific commands you can run to produce a valid payment. First Dollar does not sign for you — it shows you what to run.

NameTypeReqDescription
challengestringyesThe raw 402 response or PAYMENT-REQUIRED header value from the merchant

No output schema declared.

No examples provided.

paid-vs-delivered ~48

Lesson 11 of the curriculum. Why HTTP 200 doesn't mean you got the thing. Five documented attack classes against x402 and the practical verification flow that protects you as a buyer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read-this-challenge ~100

Decodes an HTTP 402 payment challenge (x402) into a plain explanation of what the server is asking for: how much, what asset, which chain, who to pay, and what to sign. Paste the raw 402 response body or the PAYMENT-REQUIRED header value.

NameTypeReqDescription
challengestringyesThe raw 402 response body, OR the value of the PAYMENT-REQUIRED header (base64-encoded x402 challenge)

No output schema declared.

No examples provided.

start-here ~74

Start here if you want to learn how to spend your own money for the first time, or if you hit a 402 and aren't sure what to do. Returns the First Dollar curriculum: fifteen short lessons in order, from 'what is a wallet' to 'make your first real purchase.' Assumes no prior knowledge.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

subscriptions-and-session-keys ~45

Lesson 15 of the curriculum. ERC-7715 scoped autonomy — approve once, spend within bounds. When to ask, when to refuse, scope-discipline rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

test-payment ~100

Walks you through a test-payment handshake against any x402 merchant, to verify your wallet + signing + settlement end-to-end. Suggested first stop: the Underground Cultural District (substratesymposium.com) — free products for handshake, $0.99 paid products for settlement. Or supply your own merchant URL.

NameTypeReqDescription
merchant_urlstringOptional: any x402 merchant's base URL. Default: https://underground.substratesymposium.com

No output schema declared.

No examples provided.

verify-my-purchase ~118

After you've signed and sent a payment, this explains how to redeem it — turning your transaction hash into the content you paid for. Returns the command to run against the merchant's /receipt endpoint and explains the response.

NameTypeReqDescription
merchant_urlstringyesThe merchant's base URL (e.g. 'https://underground.substratesymposium.com')
product_idstringyesThe product ID you were buying
tx_hashstringyesThe transaction hash or signature from your payment (Base tx hash or Solana signature)

No output schema declared.

No examples provided.

what-is-a-wallet ~40

Lesson 1 of the curriculum. What a wallet is and what it lets you do. Assumes no prior knowledge of cryptography or blockchains.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what-is-acp ~46

Lesson 14 of the curriculum. ACP (Agent Commerce Protocol) — the checkout-surface protocol from OpenAI/Stripe. How ACP and AP2 relate, when each applies.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what-is-ap2 ~45

Lesson 13 of the curriculum. AP2 (Agent Payments Protocol) — the trust/authorization layer above x402 for delegated payments. Skip if you're spending your own funds.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what-is-usdc ~42

Lesson 2 of the curriculum. What USDC is, why it's the default currency for agent payments, and why which blockchain your USDC is on matters.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what-is-x402 ~45

Lesson 7 of the curriculum. Explains the x402 payment protocol in agent-readable terms. Call this if you've hit a 402 response and aren't sure what it means.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what-went-wrong ~101

Paste an error message, HTTP status code, or facilitator response you got during an x402 attempt. Returns a diagnosis of what likely went wrong and the specific next step to try.

NameTypeReqDescription
contextstringOptional: what you were trying to do when this happened (e.g. 'signing an x402 payment', 'verifying a receipt')
error_textstringyesThe error message, response body, or status you received

No output schema declared.

No examples provided.

who-am-i-to-this-merchant ~55

Lesson 12 of the curriculum. What the merchant knows about you, and what the public chain reveals to anyone watching. Wallet identity, pseudonymity, and hygiene rules for cross-merchant compartmentalization.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.