/settings/billing cover the whole account, not one MCP, for the current month.
What the cost figure means
The same thing it means everywhere else in MCPulse: what your servers cost the people running them, in context, this month. It is not what MCPulse charges you — that is your plan, and it does not move with your traffic. It uses the same two constants as cost per session, from the same service, so an account-wide figure and a per-MCP figure cannot disagree about arithmetic.The month is a UTC month
Like every other date boundary in the product. See Date ranges.The calls meter is the one that bites
Calls this month is metered against your plan, and reaching it stops recording: ingest answers402, a banner appears above the overview, this meter turns red, and the chart is flat from the moment it stopped.
Your server is unaffected. The SDK treats any non-2xx as a failed batch and drops it, exactly as it treats a network failure, so a cap costs you data and never a tool call.
The verdict is cached for a minute, the same way an API key is — a database round trip per batch is a round trip inside somebody’s tool call. So going over, or upgrading, takes up to a minute to take effect.
Sample data is excluded. The
Acme Orders MCP every new account is seeded with carries thousands of fabricated calls; counting them would open a brand-new account a third of the way through its allowance having made no calls at all.The other limits
Separately from all of these there is an ingest rate limit — 10,000 payloads per minute per key — which protects the API rather than metering a plan. See Rate limits.