​
Overview

There are several ways to deploy remote MCP servers to be publically accessible. TollBit uniquely provides a simple way to publish MCP servers such that they can be easily discoverable and monetized.

Deploying a remote MCP server typically involves a very rudimentary setup of some stdio server acting as if it were run locally. We don’t believe this is a realistic approach that will support a thriving MCP ecosystem.

Application specific API keys and accounts are a clear bottleneck to the adoption of MCP for developers and end users.

If service providers are going to open up their own application interface to the public by means of MCP, they must be able to monetize it.

TollBit’s infrastructure makes this very easy.

​
TollBit Tokens

TollBit tokens are a simple standard that allows MCP server owners to monetize and manage access to their servers.

Integrating with TollBit means accepting TollBit Tokens as a part of requests made to your MCP server.

curl -X POST http://your-mcp-server.com \
  -H "Authorization: Bearer <tollbit-token>" \
  -H "Content-Type: application/json" \
  -d '{"key": "value"}'

When a request is made to your MCP server, TollBit will validate the TollBit token and make it available to your server. Then, your server can use its claims in a number of ways.

  1. Use the claims to determine if the request should be granted access.
  2. Use the claims to determine how much to bill the user.
  3. Use the claims to determine which user the request should be attributed to.

By accepting TollBit tokens, MCP server owners can easily monetize and authenticate requests to their servers.

​
Accepting TollBit tokens

Coming soon!

Both managed and self-hosted MCP servers can accept TollBit tokens.

​
Managed MCP Servers

Managed MCP servers are hosted and managed by TollBit.

​
Self-Hosted MCP Servers

Self-hosted MCP servers are hosted by the MCP server owner.