# three.ws Billing (npm · @three-ws/billing-mcp)

An agent's account economics — plan quotas, metered usage, invoices, receipts, and earnings.

- Trust score: 66/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@three-ws/billing-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/nirholas-billing-mcp/three-ws-billing-mcp.md), [page](https://verifymcp.io/servers/nirholas-billing-mcp/three-ws-billing-mcp)

## Channel facts

- Registry: `npm`
- Package: `@three-ws/billing-mcp`
- Version: `0.1.1`
- 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-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 29 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1603 tokens (~267/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add nirholas-billing-mcp -- npx -y @three-ws/billing-mcp
```

### Codex

```bash
codex mcp add nirholas-billing-mcp -- npx -y @three-ws/billing-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nirholas-billing-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@three-ws/billing-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nirholas-billing-mcp --command npx --arg -y --arg @three-ws/billing-mcp
```

### Hermes

```yaml
mcp_servers:
  nirholas-billing-mcp:
    command: "npx"
    args: ["-y", "@three-ws/billing-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "nirholas-billing-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/billing-mcp"
      ]
    }
  }
}
```

## 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-03 (score 66, +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.

### 2026-08-02 (score 65, +47)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: Apache-2.0

### 2026-07-31 (score 18, −6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 24, 0)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −18)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 42)

First indexed and scored.

## MCP tools (6)

### `get_billing_summary` (~176 tokens)

My plan, quotas, and current usage

Your account's plan tier, the quota ceilings for that tier, and live usage measured against them — the "how much of my plan is left?" call. Returns `plan` (e.g. free | pro), `quotas` (max_avatars, max_bytes_per_avatar, max_total_bytes, mcp_calls_per_day — or null when the tier has no metered ceilings), and `usage` (avatar_count, total_bytes of avatar storage, agent_count, mcp_calls_24h tool calls in the last 24 hours, llm_calls_month LLM calls since the start of this UTC month). Each tool returns a `remaining` map computed from quotas − usage so an agent can see headroom at a glance. Resolved from your three.ws session; requires THREE_WS_SESSION. Read-only.

### `query_usage` (~322 tokens)

My metered usage / invoice statement for a period

Your metered usage rolled up into an invoice statement for a billing period — what you were charged for, broken down by action. Returns `period_label` + `period` ({from,to} ISO), `line_items` (one per billed action: action id, human label, count, units, gross_usd, fee_usd, gross/fee/net atomics in USDC 6dp, discount_bps holder-tier discount applied), `totals` (charge_count, gross_usd, fee_usd, net_usd, currency), and `reconciliation` (total / reconciled / unreconciled / all_reconciled — whether every charge maps to a real settlement). Defaults to the current UTC calendar month. Pass `period` (YYYY-MM) for a calendar month, or `from`/`to` (ISO-8601) for an explicit window — `period` wins if both are given. For a downloadable CSV of the same line items use export_billing_history. Requires THREE_WS_SESSION. Read-only.

Input parameters:

- `from` (string): Window start, ISO-8601 (e.g. 2026-06-01T00:00:00Z). Ignored when `period` is set.
- `period` (string): A calendar month as YYYY-MM (e.g. 2026-06). Takes precedence over from/to. Omit for the current month.
- `to` (string): Window end (exclusive), ISO-8601. Ignored when `period` is set.

### `export_billing_history` (~291 tokens)

Export my billing history as CSV

Export a billing period's usage line items as a ready-to-save CSV — the same charges query_usage returns, in spreadsheet form. Returns `filename` (suggested download name, e.g. three-ws-invoice-2026-06.csv), `content_type` (text/csv), `csv` (the full CSV text, columns: action,label,count,units,gross_usd,fee_usd,discount_bps with a trailing TOTAL row), `row_count`, and `preview` (the first few parsed rows as objects for a quick look). Same period selection as query_usage: pass `period` (YYYY-MM) or `from`/`to` (ISO-8601); defaults to the current UTC calendar month. Requires THREE_WS_SESSION. Read-only.

Input parameters:

- `from` (string): Window start, ISO-8601. Ignored when `period` is set.
- `period` (string): A calendar month as YYYY-MM (e.g. 2026-06). Takes precedence over from/to. Omit for the current month.
- `preview_rows` (integer): How many parsed line-item rows to include in `preview` (0–100, default 5). The full CSV is always returned in `csv`.
- `to` (string): Window end (exclusive), ISO-8601. Ignored when `period` is set.

### `get_receipt` (~222 tokens)

Get one receipt (per-charge or per-purchase)

Fetch a single itemized receipt you own, in one of two forms. Pass `event_id` (numeric, from a usage line item) for a per-CHARGE receipt: action, label, units, gross_usd / fee_usd / net (with USDC atomics), discount_bps + discount_percent, and a `settlement` block (kind, ref, tx_signature, network, explorer_url, token_price_usd) plus issued_at. Pass `purchase_id` (UUID) instead for the cryptographically SIGNED receipt JSON of a confirmed skill purchase (receipt + signature + issued_at). Supply exactly one. Returns the `receipt` object and which `kind` ("charge" | "purchase") it is. Requires THREE_WS_SESSION. Read-only.

Input parameters:

- `event_id`: Numeric usage-event id for a per-charge receipt (from a query_usage line item). Mutually exclusive with purchase_id.
- `purchase_id` (string): UUID of a confirmed skill purchase for its signed receipt JSON. Mutually exclusive with event_id.

### `get_revenue` (~280 tokens)

My agents’ earnings (revenue + subscriptions)

Earnings for the agents YOU own — the income side of your account economics (what you EARNED, vs what you were charged in query_usage). Returns `summary` (gross_total, fee_total, net_total in token atomics, plus payment_count, currency_mint, chain), `by_skill` (net_total + count per skill, top first), `timeseries` (net_total + count bucketed by granularity), `subscriptions` (creator-subscription income in USD — income_usd, payment_count, active_subscribers, plan_count — settled directly to your wallet, kept separate from the withdrawable pool so units never mix), `subscription_timeseries`, and `reconciliation`. Optional `agent_id` narrows to one agent; `from`/`to` set the window (default last 30 days); `granularity` is day | week | month (default day). Requires THREE_WS_SESSION. Read-only.

Input parameters:

- `agent_id` (string): Limit to a single agent you own (UUID). Omit to aggregate across all your agents.
- `from` (string): Window start, ISO-8601. Defaults to 30 days ago.
- `granularity` (string): Time-series bucket size (default day).
- `to` (string): Window end, ISO-8601. Defaults to now.

### `get_fee_info` (~92 tokens)

Current platform fee rate

The current three.ws platform fee rate — the cut taken on marketplace sales, so an agent can reason about net vs gross before a charge settles. Returns `fee_bps` (basis points, e.g. 250 = 2.5%) and `fee_percent` (the same rate as a human string, e.g. "2.5"). Public — needs no session or credential. Read-only.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nirholas-billing-mcp/three-ws-billing-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 18
- 2026-07-31: 18
- 2026-07-30: 24
- 2026-07-28: 24
- 2026-07-27: 42

## Links

- npm package: https://www.npmjs.com/package/@three-ws/billing-mcp
- Socket report: https://socket.dev/npm/package/@three-ws/billing-mcp
- Repository: https://github.com/nirholas/three.ws
- Website: https://three.ws/
- Changelog RSS feed: https://verifymcp.io/servers/nirholas-billing-mcp/three-ws-billing-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/nirholas-billing-mcp/three-ws-billing-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/nirholas-billing-mcp/three-ws-billing-mcp