Skip to content

Charge for your MCP tools.
Zero payment code.

MCP Keeper is a hosted proxy that sits between AI agents and your MCP server. Set a price per tool, and we handle payment collection, metering, and payouts — you never touch a payment API.

5 live listings9 toolsOpen beta — free to list

🔧 Your MCP Server
🛡 MCP Keeper Proxy
🤖 AI Agent pays via x402
How It Works

Three steps to revenue

Register your server, start with a controlled rollout through the proxy, and make it your default public endpoint once you are confident. Daily USDC payouts land in your Base wallet once you clear the minimum.

1

Register your MCP server

Point MCP Keeper at your existing server URL. We create a proxy endpoint you can hand to a small test group first, without shutting off your current traffic.

2

Set prices per tool

Choose a per-call price for each tool — from $0.001 microtransactions to $1+ for premium operations. Free tools stay free.

3

Agents pay, you earn

When an agent calls a paid tool through the proxy, MCP Keeper collects payment via x402 and forwards the request to your server. Once the rollout looks good, make the proxy your main public endpoint.

Why MCP Keeper

Built for the MCP ecosystem

Whether you build tools or consume them, MCP Keeper makes paid tools seamless.

🔌

Drop-in proxy

Your server stays unchanged. We proxy MCP JSON-RPC traffic and inject payment gating transparently.

💰

x402 payments

The open HTTP 402 protocol lets agents pay per request using stablecoins — no credit cards, no subscriptions.

📊

Dashboard & analytics

Track calls, revenue, and tool usage from a single dashboard. Manage servers, pricing, and payouts.

🏪

Bazaar discovery

Your tools are automatically listed in the Bazaar marketplace, so agents can discover and connect instantly.

🛡️

Rate limiting

Built-in per-server rate limits protect your infrastructure from abuse and runaway agents.

💸

USDC payouts

Add a Base wallet address and receive direct USDC payouts once you clear the minimum. We handle metering, fee accounting, and payout tracking.

Author Onboarding

What you are signing up for

MCP Keeper does not force a hard cutover. Agents only pay when they connect to the proxy URL we issue for your server, so you can start with a small slice of traffic before making it your default public endpoint.

No forced cutover on day one

1

Register your upstream

You tell MCP Keeper where your real MCP server lives. We probe tools/list, store pricing, and mint a proxy URL for agents.

2

Start with a subset of traffic

You do not need to cut over everything on day one. Send a beta group, a few partner agents, or new users to the MCP Keeper proxy URL first and keep your normal traffic flowing as-is.

3

Make the proxy your default endpoint when ready

Once you trust the payment and routing flow, update your docs and configs so the MCP Keeper URL becomes the public entrypoint for agents. If your upstream stays public and widely advertised, agents can still bypass pricing by going direct.

What agents should use

https://api.mcpkeeper.com/mcp/your-slug

This is the endpoint that returns free discovery responses, paid 402 challenges, and forwards successful paid calls to your upstream. Start by sharing it with a controlled group, then make it your default public endpoint when you trust the flow.

How to move traffic onto the payment layer

  • Start by giving the MCP Keeper proxy URL only to the users or agents you want in the paid rollout.
  • When you are confident, update your docs, examples, and marketplace listings so the proxy URL is the default public endpoint.
  • For stronger enforcement, keep your upstream unlisted or add your own gate there too: shared secret, IP allowlist, Cloudflare Access, or another origin check.

Want a custom hostname later? MCP Keeper can support that, but today it is a manual setup handled case by case rather than self-serve or automatic DNS cutover.

FAQ

What authors usually ask

The product works best when the routing story is explicit: you can roll out gradually, but paid traffic only happens on the proxy path.

Do I have to cut over all traffic to MCP Keeper right away?

No. Start with a controlled rollout. Give the proxy URL to a small group of users, partner agents, or new integrations first while your existing traffic keeps using the current path.

How do agents actually go through the payment layer?

Agents only hit the payment layer when they connect to your MCP Keeper proxy URL. That is the endpoint that returns pricing metadata, 402 payment challenges, and paid request forwarding.

Can agents bypass payment if my upstream stays public?

Yes. If your upstream remains publicly reachable and you keep advertising it, agents can still call it directly. The cleanest model is to make the MCP Keeper URL the public endpoint and keep the upstream private or protected.

Can I use my own domain or custom hostname?

Yes, but today that is handled manually by MCP Keeper. It is not an automatic self-serve DNS cutover yet, so custom hostname support is available case by case.

What tax info do I need to provide if I am U.S.-based?

If you are a U.S.-based payout recipient and your payouts reach the reporting threshold, MCP Keeper will need a signed Form W-9 so it can prepare the required IRS reporting, including Form 1099-NEC where applicable. The practical rule for authors is: expect payouts to pause once reportable payouts reach $600 until a valid W-9 is received and reviewed.

Do you support foreign payout recipients today?

Not yet. MCP Keeper currently supports U.S.-based payout recipients only. Foreign payout support needs a fuller W-8BEN or W-8BEN-E and withholding workflow that is not productized yet.

What is the recommended rollout path?

Register your upstream, issue a proxy URL, test it with a subset of traffic, confirm payments and routing behave correctly, then update your public docs and client configs so the proxy becomes the default entrypoint.

For tool authors

  • Keep your existing MCP server running while you test the proxy path
  • Set per-tool pricing from the dashboard
  • Automatic discovery via Bazaar protocol
  • Revenue analytics and payout tracking
  • Base wallet payouts with direct USDC transfers
Register as an author

For AI agents

  • Connect to any proxy URL like a normal MCP server
  • Pay per call via x402 — no API keys or accounts
  • Discover tools in the Bazaar marketplace
  • Free tools available with zero friction
  • Transparent pricing before each call
Explore tools

Ready to monetize?

Create an account, register your MCP server, and start earning in minutes.

Get Started Free →