Cap the tool. Keep the provider key.
An MCP tool server can loop model and tool calls against a standing provider secret. Issue a Till key for that server with a required request ceiling so remaining capacity stays readable and the tool can stop.
Isolate the tool traffic, not the provider account.
-
01
Issue a disposable Till key for the server
Set the request ceiling from the expected tool calls, then add optional token, estimated-spend, expiry, and IP bounds when the runtime needs a tighter envelope.
-
02
The provider credential stays behind Till
The MCP server uses a Till key, not an unconstrained provider secret in the tool process. When the server is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not an MCP runtime or tool registry
Till does not host your MCP server, register tools, or replace the client. It is a hosted control layer in front of 12 AI providers: a required request ceiling and optional token, spend, expiry, and IP controls.
-
04
Pro: $59/month, 25 scoped keys, 25,000 monthly activations
Those are plan limits. Public signup is closed; request Pro beta access. Provider inference is billed by the provider. Till charges a platform subscription.
Connect provider accounts once. Each MCP server gets a disposable Till key with a required request ceiling and optional token, estimated-spend, expiry, and IP controls. Till is not a zero-knowledge vault, an MCP host, or a replacement for provider billing or IAM.
These are plan limits, not usage claims.
Pro
Scale
Public anonymous signup is closed. New accounts are approved and provisioned manually. Existing customers can open the dashboard. Compare the full ledger on pricing.
Run the server. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.