Obolus
PYPI · OBOLUS · SCANNED AUG 21
Disposable Algorand wallet for AI agents. Pay x402 resources in USDC, no human provisioning.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1186 tokens (~395/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
pypi · obolus
claude mcp add inviti8-obolus -- uvx obolus
codex mcp add inviti8-obolus -- uvx obolus
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"inviti8-obolus": {
"type": "local",
"command": [
"uvx",
"obolus"
],
"enabled": true
}
}
} openclaw mcp add inviti8-obolus --command uvx --arg obolus
mcp_servers:
inviti8-obolus:
command: "uvx"
args: ["obolus"] {
"mcpServers": {
"inviti8-obolus": {
"command": "uvx",
"args": [
"obolus"
]
}
}
} 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.
- 14 Aug 26 61
First indexed and scored.
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 Aug 2026 · Analysed pypi/obolus@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 | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
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.
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 ~489
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. `content_type` sets the request's Content-Type. Some paid endpoints require it and reject the request without it - AFTER taking payment, because the payment is verified before the handler runs. Set it whenever the body is not plain text. Response headers the merchant set are returned under `response_headers`; some endpoints put results there that appear nowhere…
| 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.