Obolus
PYPI · OBOLUS
Disposable Algorand wallet for AI agents. Pay x402 resources in USDC, no human provisioning.
Available components
Last scanned (6 hours ago)
Scores higher than 57% of PyPI servers
Category Crypto and Web3
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
- 1 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (Apache-2.0).Pass
- Actively maintained (last published 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1277 tokens (~425/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (67% 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 −14
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
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/obolus@0.2.3
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 39 packages
| Packages resolved | 39 |
|---|---|
| No linked repository | 1 |
| 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 →
wallet_funding_info ~487
Explain how to put money in this wallet, and report which of the three setup steps the vault is on. For the human, not the agent - it returns an address and instructions, and no part of it can be automated by the agent. The three steps are in a forced order: ALGO must arrive before the vault can opt into the payment asset, and the opt-in must happen before USDC can be received at all. USDC sent to a vault that has not opted in is rejected outright - it does not sit pending, it fails. Each step a human performs carries a `scan` value: an ARC-26 URI an Algorand wallet can scan. It encodes the address AND the asset id, so the sender cannot aim at the wrong asset by hand - which matters because sending the wrong one is rejected rather than held. No amount is encoded; the human types that into their own wallet where they see it before confirming. TOPPING UP ONE ASSET. Pass `asset` - "ALGO", "USDC", or the asset id - and the reply narrows to that asset's steps AND includes the QR code as an image, so the human can scan it directly. ALGO codes are black; the payment asset's are blue and captioned, so the two are not confused at a glance. Omit `asset` for the whole picture as text. The usual flow: `wallet_status` answers "how much do I have", then `wallet_funding_info(asset="USDC")` answers "I want to top up USDC". SET `open_in_browser` WHENEVER A HUMAN WANTS TO SCAN THE CODE. The image block this returns renders in some MCP clients and not in a terminal, so on its own it can reach the model and never reach the person holding the phone. With the flag, Obolus writes a self-contained page and opens it in the default browser - no server and no network needed. `qr_dir` optionally writes the codes as PNG files into that directory, under the same configured file root as body_file/output_file. `obolus vault qr` prints them straight into a terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | – | – | – |
| open_in_browser | boolean | – | – |
| qr_dir | – | – | – |
No output schema declared.
No examples provided.
wallet_status ~87
Report the wallet's state: network, vault address and balances, the active session and what remains in it, spending so far today, and the configured caps. Read this before assuming a payment can be made. A vault that is not yet funded or not yet opted into the payment asset cannot pay for anything, and this is where that shows up. Costs nothing and spends nothing.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
x402_fetch ~580
Fetch a URL, paying automatically if it answers with an x402 payment challenge. SPENDS REAL MONEY when the network is mainnet. Payment comes from a short-lived session account funded from the user's vault, never from the vault itself, so the most any single call can lose is the session balance. Returns the response body plus, when a payment happened, the price, the merchant address, the transaction id and the settlement receipt. What the receipt proves: that this payment settled on chain. It does NOT prove the resource was correct, honest, or worth the price - a settled payment and a useful answer are different claims. Refuses, without spending, when: the price exceeds max_price_usdc or the configured per-call cap; the day's spending cap would be exceeded; the merchant is outside an allowlist the user enabled; the resource asks for an asset this wallet does not hold; the payTo address is one of ours (paying yourself is not a payment); or a mainnet resource is not https. Each refusal says which rule it hit. Unpaid URLs are fine - if the server answers normally, the body is returned and nothing is spent. FILES. `body_file` sends the bytes at a path instead of `body`, and `output_file` writes the response to a path instead of returning it inline. Use them for anything binary or large - an image to be signed, a document to be processed - because binary cannot survive being passed as text and a large body would swamp the conversation. Both are confined to a directory the user configured, and both are DISABLED unless they configured one; a path outside it is refused. Pass `body` or `body_file`, never both. JSON. Pass `body` as an object or array, not as a string of JSON - it is sent as `application/json` and you do not need to set `content_type`. A string `body` is sent verbatim, which is what you want for text, XML or form encoding. If the exact bytes matter - anything the endpoint hashes or signs over - use `body_file`, which is never re-encoded. `content_type`…
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| body_file | – | – | – |
| content_type | – | – | – |
| max_price_usdc | – | – | – |
| method | string | – | – |
| output_file | – | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Obolus MCP server?
Obolus runs locally as a PyPI package, launched with uvx obolus. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · obolus
claude mcp add inviti8-obolus -- uvx obolus
What is the Obolus MCP server?
Obolus is an MCP server listed in the public MCP registry as io.github.inviti8/obolus. Disposable Algorand wallet for AI agents. Pay x402 resources in USDC, no human provisioning. This page covers its PyPI package (obolus).
Is the Obolus MCP server safe to use?
Obolus scores 60 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 Obolus MCP server expose?
Obolus exposes 3 tools: x402_fetch, wallet_status, wallet_funding_info. Their descriptions and schemas cost roughly 1,154 tokens of context every time the server is loaded.
Is the Obolus MCP server still maintained?
Obolus 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 Obolus MCP server under?
Obolus declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.