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.

Obol

NPM · @SUPERBIGROACH/OBOL-MCP

Find, pay for & call APIs in USDC from AI agents - gasless, sub-cent, 0% commission.

0 this week 76 Trust /100

Last scanned (18 hours ago)

Scores higher than 53% of npm servers

Category Finance and Payments

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 41 of 139 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 498 tokens (~99/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • Stability: 0.97 → pass security
  • 20 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 14 Nov 26 +1
    • Stability: 0.97 → pass security
  • 12 Nov 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.

  • 10 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 7 Nov 26 +1

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

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 21 Nov 2026 · Analysed npm/@superbigroach/obol-mcp@0.2.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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 139 packages
Packages resolved 139
Stale 40
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~498 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
deposit ~49

Fund the agent's Gateway balance once (gas-free spending afterward). Amount in USDC, e.g. '5'.

NameTypeReqDescription
amountstringyesUSDC amount to deposit, e.g. '5'
NameTypeReqDescription
depositedstring––
errorstring––
okbooleanyes–
txstring––

No examples provided.

find_service ~92

Search the Obol directory for metered APIs an agent can pay for per call. Results are relevance-ranked (name > category > description). Returns id, price (USDC), description, the callable URL, and a relevance score.

NameTypeReqDescription
limitnumber–max results to return (default 20)
querystring–what you need, e.g. 'crypto prices' or 'web scraper'
NameTypeReqDescription
countnumberyes–
notestring––
servicesarrayyes–

No examples provided.

get_balance ~22

Get the agent wallet + Gateway USDC balances on Arc testnet.

Input schema present but exposes no named parameters.

NameTypeReqDescription
addressstring––
errorstring––
gatewayAvailableUsdcstring––
okbooleanyes–
walletUsdcstring––

No examples provided.

list_service ~183

List (publish) a new service on the Obol marketplace so other agents can discover and pay for it. Requires the seller's Obol API key (OBOL_API_KEY env). Obol auto-issues a real ACK-ID verifiable credential for the seller's wallet and returns the marketplace URL.

NameTypeReqDescription
categorystring–e.g. Data, AI, Scraper, Tools
descriptionstring––
docsUrlstring––
hostedUrlstringyesthe public https:// endpoint agents will call
inputSchemastring–input params, e.g. 'coin: string'
namestringyesshort service name, e.g. 'Crypto Price API'
priceUsdcstringyesUSDC price per call, e.g. '0.001'
skillMarkdownstring––
NameTypeReqDescription
ackDidstring––
ackIssuerstring––
errorstring––
marketplaceUrlstring––
messagestring––
okbooleanyes–

No examples provided.

pay_and_call ~152

Pay for and call an Obol metered service via Circle Gateway. Enforces your per-call maxPrice and (with OBOL_API_KEY) your account's daily/weekly/monthly spending limits. Near-limit pays ask you to confirm. Idempotent on retry. Returns the result plus a signed, verifiable payment receipt.

NameTypeReqDescription
callUrlstringyesthe service's callUrl from find_service
idempotencyKeystring–reuse across retries; auto-generated if omitted
maxPricenumber–max USDC to pay for this call (default 1.0)
methodstring––
paramsobject–query params to pass to the API
NameTypeReqDescription
data–––
declinedboolean––
errorstring––
idempotencyKeystring––
limitRemainingnumber––
okbooleanyes–
paidstring––
receipt–––
receiptSignaturestring––
responseSafetyobject––
txstring––
warningstring––

No examples provided.

Install

How do I install the Obol MCP server?

Obol runs locally as an npm package, launched with npx -y @superbigroach/obol-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 · @superbigroach/obol-mcp

# add to Claude Code
claude mcp add superbigroach-obol -- npx -y @superbigroach/obol-mcp
Common questions

What is the Obol MCP server?

Obol is an MCP server listed in the public MCP registry as io.github.superbigroach/obol. Find, pay for & call APIs in USDC from AI agents - gasless, sub-cent, 0% commission. This page covers its npm package (@superbigroach/obol-mcp).

Is the Obol MCP server safe to use?

Obol scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 Obol MCP server expose?

Obol exposes 5 tools: find_service, deposit, pay_and_call, list_service, get_balance. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.

Is the Obol MCP server still maintained?

Obol is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Obol MCP server?

VerifyMCP ran 16 checks on Obol, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.