Read token metadata, applications, audit logs, proxies and usage in the PCI vault. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"basis-theory": {
"url": "https://basis-theory.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"basis-theory": {
"type": "http",
"url": "https://basis-theory.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Basis Theory API key.
Create a READ-ONLY management key in the Basis Theory portal → Applications. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Basis Theory API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Basis Theory connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
basis_theory_list_tokens | read | List tokens List vault tokens as METADATA — id, type, container, fingerprint, metadata and timestamps. Does not return the underlying card number or PII. Basis Theory: GET /v2/tokens. |
basis_theory_search_tokens | read | Search tokens Search tokens with Basis Theory's query syntax over metadata, e.g. metadata.customer_id:"cus_1". Returns metadata only. Read-only despite being a POST — the query goes in the body. Basis Theory: POST /v2/tokens/search. |
basis_theory_get_token | read | Get one token Fetch a single token by id. Returns metadata, container, fingerprint and timestamps. WARNING: if the configured API key carries a reveal permission, the response also contains the token's plaintext data — issue this server a read-only management key instead. Basis Theory: GET /tokens/{id}. |
basis_theory_list_applications | read | List applications List the applications (API-key holders) in the tenant, with their types and permissions. Basis Theory: GET /applications. |
basis_theory_get_application | read | Get one application Fetch a single application with its type and permission list. Basis Theory: GET /applications/{id}. |
basis_theory_whoami | read | Identify the configured key Return the application the configured BT-API-KEY belongs to — the fastest way to check which permissions this server actually has. Basis Theory: GET /applications/key. |
basis_theory_list_logs | read | List audit logs List audit-log entries — who did what to which entity and when. The tool for answering 'who touched this token?'. Basis Theory: GET /logs. |
basis_theory_list_log_entity_types | read | List log entity types List the entity types the audit log records — the valid values for entity_type. Basis Theory: GET /logs/entity-types. |
basis_theory_list_proxies | read | List proxies List the proxies that forward requests to third parties, detokenizing in flight. Basis Theory: GET /proxies. |
basis_theory_get_proxy | read | Get one proxy Fetch a single proxy with its destination URL and transform configuration. Basis Theory: GET /proxies/{id}. |
basis_theory_list_reactors | read | List reactors List reactors — the serverless functions that run against detokenized data inside the vault. Basis Theory: GET /reactors. |
basis_theory_get_reactor | read | Get one reactor Fetch a single reactor with its configuration. Basis Theory: GET /reactors/{id}. |
basis_theory_list_permissions | read | List permissions List the permissions that can be granted to an application, optionally for one application type. Basis Theory: GET /permissions. |
basis_theory_list_roles | read | List roles List the roles available for tenant members. Basis Theory: GET /roles. |
basis_theory_get_tenant | read | Get the tenant Fetch the current tenant — name, id and settings. Basis Theory: GET /tenants/self. |
basis_theory_get_tenant_usage | read | Get the tenant usage report Fetch the tenant's usage report — token counts by type and container, and monthly API call volume. Basis Theory: GET /tenants/self/reports/usage. |
basis_theory_list_tenant_members | read | List tenant members List the people with access to the tenant, and their roles. Basis Theory: GET /tenants/self/members. |
basis_theory_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
basis_theory_request_feature | Request a missing feature Tell usefulapi that the user needs something the Basis Theory tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
basis_theory_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Basis Theory tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
basis_theory_cancel_subscription | Cancel the Pro subscription Cancel the caller's Basis Theory Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run basis_theory_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Basis Theory server only. Subscribe with basis_theory_upgrade (it returns a Stripe Checkout link). Cancel any time with basis_theory_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running basis_theory_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Basis Theory. The server calls the Basis Theory API with your own Basis Theory access, so it sees only the data that your account can see.
The login page asks for your Basis Theory API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Basis Theory API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Basis Theory API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Basis Theory.
All 17 Basis Theory tools are marked read-only.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Basis Theory server only. Run basis_theory_usage_status to see how many calls you used.
Ask the AI to run basis_theory_upgrade: it returns a Stripe Checkout link. To cancel, run basis_theory_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with basis_theory_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.