three.ws Billing
NPM · @THREE-WS/BILLING-MCP · SCANNED SEP 23
An agent's account economics — plan quotas, metered usage, invoices, receipts, and earnings.
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- 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: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the three.ws Billing MCP server?
three.ws Billing runs locally as an npm package, launched with npx -y @three-ws/billing-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 · @three-ws/billing-mcp
claude mcp add nirholas-billing-mcp -- npx -y @three-ws/billing-mcp
{
"mcpServers": {
"nirholas-billing-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/billing-mcp"
]
}
}
} {
"servers": {
"nirholas-billing-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/billing-mcp"
]
}
}
} codex mcp add nirholas-billing-mcp -- npx -y @three-ws/billing-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-billing-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/billing-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-billing-mcp --command npx --arg -y --arg @three-ws/billing-mcp
mcp_servers:
nirholas-billing-mcp:
command: "npx"
args: ["-y", "@three-ws/billing-mcp"] {
"McpServers": {
"nirholas-billing-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/billing-mcp"
]
}
}
} assistant mcp add nirholas-billing-mcp -t stdio -c npx -a -y @three-ws/billing-mcp
{
"mcpServers": {
"nirholas-billing-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/billing-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −4
- Stability: pass → 0.77 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- Package version: 0.1.1 → 0.1.2 functional
- 16 Sept 26 −1
- Stability: pass → 0.93 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 23 Sept 2026 · Analysed npm/@three-ws/billing-mcp@0.1.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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
export_billing_history Export my billing history as CSV ~291
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_billing_summary My plan, quotas, and current usage ~176
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fee_info Current platform fee rate ~92
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_receipt Get one receipt (per-charge or per-purchase) ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_revenue My agents’ earnings (revenue + subscriptions) ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
query_usage My metered usage / invoice statement for a period ~322
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
What is the three.ws Billing MCP server?
three.ws Billing is an MCP server listed in the public MCP registry as io.github.nirholas/billing-mcp. An agent's account economics, plan quotas, metered usage, invoices, receipts, and earnings. This page covers its npm package (@three-ws/billing-mcp).
Is the three.ws Billing MCP server safe to use?
three.ws Billing scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 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 three.ws Billing MCP server expose?
three.ws Billing exposes 6 tools: get_billing_summary, query_usage, export_billing_history, get_receipt, get_revenue, get_fee_info. Their descriptions and schemas cost roughly 1,383 tokens of context every time the server is loaded.
Is the three.ws Billing MCP server still maintained?
three.ws Billing is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.