basis-theory

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 648 ms.

From one check a day over the last 2 days. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checked

Past outages lasted 1 day before it answered again.

Compare: the most reliable servers in Data, search and analytics, ranked by days answering.

Tools

17 tools: 17 read-only, 0 change data, 0 high risk (delete, pay, send or run code).

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 2,360 tokens of tool definitions and a 648 ms handshake.

• read-onlybasis_theory_list_tokensList 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.
• read-onlybasis_theory_search_tokensSearch 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.
• read-onlybasis_theory_get_tokenFetch 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}.
• read-onlybasis_theory_list_applicationsList the applications (API-key holders) in the tenant, with their types and permissions. Basis Theory: GET /applications.
• read-onlybasis_theory_get_applicationFetch a single application with its type and permission list. Basis Theory: GET /applications/{id}.
• read-onlybasis_theory_whoamiReturn 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.
• read-onlybasis_theory_list_logsList audit-log entries - who did what to which entity and when. The tool for answering 'who touched this token?'. Basis Theory: GET /logs.
• read-onlybasis_theory_list_log_entity_typesList the entity types the audit log records - the valid values for entity_type. Basis Theory: GET /logs/entity-types.
• read-onlybasis_theory_list_proxiesList the proxies that forward requests to third parties, detokenizing in flight. Basis Theory: GET /proxies.
• read-onlybasis_theory_get_proxyFetch a single proxy with its destination URL and transform configuration. Basis Theory: GET /proxies/{id}.
• read-onlybasis_theory_list_reactorsList reactors - the serverless functions that run against detokenized data inside the vault. Basis Theory: GET /reactors.
• read-onlybasis_theory_get_reactorFetch a single reactor with its configuration. Basis Theory: GET /reactors/{id}.
• read-onlybasis_theory_list_permissionsList the permissions that can be granted to an application, optionally for one application type. Basis Theory: GET /permissions.
• read-onlybasis_theory_list_rolesList the roles available for tenant members. Basis Theory: GET /roles.
• read-onlybasis_theory_get_tenantFetch the current tenant - name, id and settings. Basis Theory: GET /tenants/self.
• read-onlybasis_theory_get_tenant_usageFetch the tenant's usage report - token counts by type and container, and monthly API call volume. Basis Theory: GET /tenants/self/reports/usage.
• read-onlybasis_theory_list_tenant_membersList the people with access to the tenant, and their roles. Basis Theory: GET /tenants/self/members.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/basis-theory.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/basis-theory.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=basis-theory.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/basis-theory.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/basis-theory.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=basis-theory.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.