mcp-metering
Free
MIT open-source package
- Included scope
- Metering policy only; no auth or Stripe integration
MCP-Billing
● Identity checkedMCP authentication and billing boilerplate · Official-source review 2026-10-09
MCP-Billing supplies source code for OAuth 2.1 with PKCE, API keys, Redis rate limiting and Stripe usage billing around MCP servers. It defines retry deduplication and partial-stream handling separately from server business logic.
- Category
- MCP authentication and billing boilerplate
- Free access
- Separate MIT mcp-metering npm package is free. It handles metering policy, not the boilerplate’s OAuth, keys, quotas, rate limiting or Stripe integration.
- API access
- Framework-independent auth and billing endpoints for MCP servers; Stripe and Redis configuration required. Exact deployment requirements need source documentation.
Is MCP-Billing right for you?
A good fit for
Relevant to developers reviewing purchased infrastructure code for a monetized MCP service.
Before you choose
EUR79 once during initial release window, advertised EUR149 afterward; charged in EUR. Commercial license allows unlimited personal/client projects but prohibits boilerplate resale. Support through GitHub issues for sixty days; seven-day refund conditional on environment incompatibility not fixed through issues. You maintain purchased code and provider updates. Same idempotency key bills once; partial/failed calls excluded by default and completed streams emit one usage event. These are documented designs, not tested billing behavior here. No package install, payment, credentials or production integration performed.
Workflow and handoff
Inspect the free metering code and purchased license, then run synthetic retry, partial-stream and webhook cases before accepting real payments.
Pricing and practical limits
EUR79 once during initial release window, advertised EUR149 afterward; charged in EUR. Commercial license allows unlimited personal/client projects but prohibits boilerplate resale. Support through GitHub issues for sixty days; seven-day refund conditional on environment incompatibility not fixed through issues. You maintain purchased code and provider updates. Same idempotency key bills once; partial/failed calls excluded by default and completed streams emit one usage event. These are documented designs, not tested billing behavior here. No package install, payment, credentials or production integration performed.
Review method
Official product evidence reviewed on 2026-10-09; product artwork inspected visually. No hands-on vendor application test was performed. Application performance, security claims and plan enforcement were not independently tested.
What it can do
Features & capabilities
Unknown is different from unavailable. Each fact carries its own evidence.
| Capability | Value | Evidence | Checked |
|---|---|---|---|
| Product workflow | MCP-Billing supplies source code for OAuth 2.1 with PKCE, API keys, Redis rate limiting and Stripe usage billing around MCP servers. It defines retry deduplication and partial-stream handling separately from server business logic. | Facts sourced | 2026-10-09 |
| Pricing and restrictions | EUR79 once during initial release window, advertised EUR149 afterward; charged in EUR. Commercial license allows unlimited personal/client projects but prohibits boilerplate resale. Support through GitHub issues for sixty days; seven-day refund conditional on environment incompatibility not fixed through issues. You maintain purchased code and provider updates. Same idempotency key bills once; partial/failed calls excluded by default and completed streams emit one usage event. These are documented designs, not tested billing behavior here. No package install, payment, credentials or production integration performed. | Facts sourced | 2026-10-09 |
Understand the total cost
MCP-Billing pricing & plans
Full boilerplate
Not listed
EUR79 introductory once; EUR149 afterward
- Included scope
- Auth, keys, Redis limits, Stripe and multi-tenant code
Alternatives to MCP-Billing
View all ↗
ArambAramb combines model routing, voice, browser execution, sandboxes, memory, tool integrations and usage billing for AI-agent products. It supports no-code authoring and developer integration within a shared credit system.
Explore tool
RunInfraRunInfra provides hosted open models through OpenAI- and Anthropic-compatible APIs. It offers prepaid token billing and workspace coding plans, with session-aware caching and separately reported cached-token usage.
Explore tool
Actx0Actx0 stores agent sessions and extracts compact memories for semantic retrieval before the next model reply. Managed workspaces include knowledge search, memory consolidation, keys, audit events and usage tracking.
Explore toolThe practical questions
Frequently asked questions
Was the application hands-on tested?
No. This listing is based on dated official-source evidence and a visual artwork check. Unconfirmed costs and restrictions are identified explicitly.
What is MCP-Billing used for?
MCP-Billing supplies source code for OAuth 2.1 with PKCE, API keys, Redis rate limiting and Stripe usage billing around MCP servers. It defines retry deduplication and partial-stream handling separately from server business logic.
Does MCP-Billing have a free plan?
Separate MIT mcp-metering npm package is free. It handles metering policy, not the boilerplate’s OAuth, keys, quotas, rate limiting or Stripe integration.. This record lists ongoing free access; check the plan limits before starting.
How much does MCP-Billing cost?
No paid monthly price is listed; this record treats the product as free to start. See the plan cards for entitlements, billing commitments and seat minimums.
Can I use MCP-Billing through an API?
Framework-independent auth and billing endpoints for MCP servers; Stripe and Redis configuration required. Exact deployment requirements need source documentation.. API access and subscription access may have different terms; consult the linked sources.
What should I check before choosing it?
EUR79 once during initial release window, advertised EUR149 afterward; charged in EUR. Commercial license allows unlimited personal/client projects but prohibits boilerplate resale. Support through GitHub issues for sixty days; seven-day refund conditional on environment incompatibility not fixed through issues. You maintain purchased code and provider updates. Same idempotency key bills once; partial/failed calls excluded by default and completed streams emit one usage event. These are documented designs, not tested billing behavior here. No package install, payment, credentials or production integration performed.
Price history
No retained pricing changes yet. A current price alone does not establish a historical trend.
How this profile is supported
Official product information
Current official product source read individually; product artwork inspected visually.
Read original source ↗Pricing review
Official product page reviewed for disclosed costs; unverified prices and allowances are identified in the listing.
Read original source ↗Facts apply to the named version and check date. Send a sourced correction if something changed.