# Obolus (pypi · obolus)

Disposable Algorand wallet for AI agents. Pay x402 resources in USDC, no human provisioning.

- Trust score: 61/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-21

## Components

- pypi · `obolus`: 61/100 (this document), [markdown](https://verifymcp.io/servers/inviti8-obolus/obolus.md), [page](https://verifymcp.io/servers/inviti8-obolus/obolus)

## Channel facts

- Registry: `pypi`
- Package: `obolus`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 2 of 41 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### Claude

```bash
claude mcp add inviti8-obolus -- uvx obolus
```

### Codex

```bash
codex mcp add inviti8-obolus -- uvx obolus
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "inviti8-obolus": {
      "type": "local",
      "command": [
        "uvx",
        "obolus"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add inviti8-obolus --command uvx --arg obolus
```

### Hermes

```yaml
mcp_servers:
  inviti8-obolus:
    command: "uvx"
    args: ["obolus"]
```

### Other

```json
{
  "mcpServers": {
    "inviti8-obolus": {
      "command": "uvx",
      "args": [
        "obolus"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-14 (score 61)

First indexed and scored.

## MCP tools (3)

### `x402_fetch` (~489 tokens)

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…

Input parameters:

- `body`
- `body_file`
- `content_type`
- `max_price_usdc`
- `method` (string)
- `output_file`
- `url` (string, required)

### `wallet_status` (~87 tokens)

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.

### `wallet_funding_info` (~487 tokens)

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.

Input parameters:

- `asset`
- `open_in_browser` (boolean)
- `qr_dir`

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/inviti8-obolus/obolus#diagnostics

## Score history

- 2026-08-21: 61
- 2026-08-20: 61
- 2026-08-19: 61
- 2026-08-18: 61
- 2026-08-17: 61
- 2026-08-16: 61
- 2026-08-15: 61
- 2026-08-14: 61

## Links

- PyPI project: https://pypi.org/project/obolus/
- Socket report: https://socket.dev/pypi/package/obolus
- Repository: https://github.com/inviti8/Obolus
- Changelog RSS feed: https://verifymcp.io/servers/inviti8-obolus/obolus.xml
- Changelog JSON feed: https://verifymcp.io/servers/inviti8-obolus/obolus.json
- HTML version of this page: https://verifymcp.io/servers/inviti8-obolus/obolus