Usage and Invoices

This page explains how mctx counts requests, calculates your hosting fee, and collects payment each month.

Request Counting

Requests are counted per MCP server, per calendar month. Each MCP server has its own independent counter that resets on the 1st of every month at midnight UTC.

A developer with three MCP servers has three separate counters. An MCP server with 800 requests and another with 1,200 requests in the same month means one MCP server stays within the free tier and one is billed for 200 requests above the threshold.

For a complete list of which MCP method calls count as requests, see How Pricing Works.

Where to See Your Usage

Your current request count is visible in two places:

• MCP server detail page — Each MCP server shows its running request total for the current month alongside a free-tier progress indicator
• Usage view — The usage section of your developer dashboard lists all your MCP servers with their current month counts

Usage data updates in near-real time. If you are watching an MCP server approach the 1,000-request threshold, the MCP server detail page is the most direct place to monitor it.

How the Monthly Billing Cycle Works

1. Requests accumulate throughout the calendar month on a per-MCP-server basis
2. On the 1st of the following month, the billing cron runs and calculates the hosting fee for every MCP server that exceeded 1,000 requests during the prior month
3. An invoice is created in your billing account for the total hosting fee across all your MCP servers
4. Your card is charged automatically — no action required on your part

The billing cron runs once per month. You are not charged mid-month for usage, even if your MCP server crosses tier boundaries partway through.

Graduated Tier Math Example

Hosting fees use graduated billing. Each tier rate applies only to requests within that band — not to the total.

Example: 15,000 requests in a month

The first 1,000 are always free. Tier 1 ($1.00/1K) covers the next 9,000 (up to 10,000 total). Tier 2 ($0.85/1K) covers the remaining 5,000. See How Pricing Works for the full rate table.

Developers with Multiple MCP Servers

If you own multiple MCP servers, a single invoice covers all of them. Each MCP server that exceeded 1,000 requests in the prior month appears as a separate line item. MCP servers within the free tier do not appear on the invoice.

One payment method covers every MCP server in your account — there is no per-server billing configuration.

Invoice Delivery

Hosting fee invoices are collected automatically against the card on file at the start of each month. Your card issuer sends a payment confirmation when the charge succeeds.

mctx does not send a separate invoice email. If you need a record of a past invoice, you can access billing history in Dev → Payouts → Billing History.

Failed Payments

If the charge against your card fails, payment retries automatically over up to 7 days using smart retry logic.

If all retries fail:

• Every MCP server you own that has previously crossed the 1,000-request threshold is suspended immediately
• You receive an email notification
• Your dashboard shows a persistent banner with a link to update your payment method

Once you update your payment method, your suspended MCP servers resume automatically.

To avoid service interruptions, keep your card up to date. You can update your card at any time in Dev → Payouts → Payment Method — you do not need to wait for a failed payment.

Next Steps

• Payment Method — How to add a card, what happens at the threshold, and the card removal warning
• How Pricing Works — Tier rates, what counts as a request, and optional monetization

See something wrong? Report it or suggest an improvement — your feedback helps make these docs better.