Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

three.ws Billing

NPM · @THREE-WS/BILLING-MCP

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

0 this week 78 Trust /100

Last scanned (14 hours ago)

Scores higher than 59% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 70 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 1294 tokens (~258/item across 5 items; 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 −2
    • Stability: fail → 0.70 functional
  • 24 Oct 26 −4
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
Diagnostics

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 Nov 2026 · Analysed npm/@three-ws/billing-mcp@0.1.3

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,103 tokens

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 →

Tool Tokens
export_billing_history ~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.

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

No output schema declared.

No examples provided.

get_billing_summary ~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 ~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 ~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.

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

No output schema declared.

No examples provided.

query_usage ~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.

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

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add nirholas-billing-mcp -- npx -y @three-ws/billing-mcp
Common questions

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 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 5 tools: get_billing_summary, query_usage, export_billing_history, get_receipt, get_fee_info. Their descriptions and schemas cost roughly 1,103 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 21 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 three.ws Billing MCP server under?

three.ws Billing 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.

What did VerifyMCP test on the three.ws Billing MCP server?

VerifyMCP ran 16 checks on three.ws Billing, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.