io.usefulapi/basis-theory
REMOTE · BASIS-THEORY.USEFULAPI.IO · SCANNED OCT 3
Read token metadata, applications, audit logs, proxies and usage in the PCI vault.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1164 tokens (~68/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/basis-theory MCP server?
io.usefulapi/basis-theory is a hosted endpoint at https://basis-theory.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · basis-theory.usefulapi.io
claude mcp add --transport http io-usefulapi-basis-theory 'https://basis-theory.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-basis-theory": {
"url": "https://basis-theory.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-basis-theory": {
"type": "http",
"url": "https://basis-theory.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-basis-theory] url = "https://basis-theory.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-basis-theory": {
"type": "remote",
"url": "https://basis-theory.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-basis-theory --url 'https://basis-theory.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-basis-theory:
url: "https://basis-theory.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-basis-theory": {
"Transport": "http",
"Url": "https://basis-theory.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-basis-theory -t streamable-http -u 'https://basis-theory.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-basis-theory": {
"type": "http",
"url": "https://basis-theory.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Oct 26 −2
- Authorization: pass → fail ▼ security
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +4
- HTTPS: unverified → pass ▲ security
- First check of Authorization: partial security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +45
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 28
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Oct 2026 · Probed https://basis-theory.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of basis-theory.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://basis-theory.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://basis-theory.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://basis-theory.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://basis-theory.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://basis-theory.usefulapi.io/mcp | HTTPS enforced | 301 | https://basis-theory.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
basis_theory_get_application Get one application ~42
Fetch a single application with its type and permission list. Basis Theory: GET /applications/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id. |
No output schema declared.
No examples provided.
basis_theory_get_proxy Get one proxy ~45
Fetch a single proxy with its destination URL and transform configuration. Basis Theory: GET /proxies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| proxy_id | string | yes | The proxy's id. |
No output schema declared.
No examples provided.
basis_theory_get_reactor Get one reactor ~42
Fetch a single reactor with its configuration. Basis Theory: GET /reactors/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| reactor_id | string | yes | The reactor's id. |
No output schema declared.
No examples provided.
basis_theory_get_tenant Get the tenant ~32
Fetch the current tenant — name, id and settings. Basis Theory: GET /tenants/self.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
basis_theory_get_tenant_usage Get the tenant usage report ~46
Fetch the tenant's usage report — token counts by type and container, and monthly API call volume. Basis Theory: GET /tenants/self/reports/usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
basis_theory_get_token Get one token ~80
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| token_id | string | yes | The token's id. |
No output schema declared.
No examples provided.
basis_theory_list_applications List applications ~90
List the applications (API-key holders) in the tenant, with their types and permissions. Basis Theory: GET /applications.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (offset pagination). |
| size | integer | – | Page size, 1-100. |
| type | string | – | Only applications of this type, e.g. private, public, management, expiring. |
No output schema declared.
No examples provided.
basis_theory_list_log_entity_types List log entity types ~38
List the entity types the audit log records — the valid values for entity_type. Basis Theory: GET /logs/entity-types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
basis_theory_list_logs List audit logs ~137
List audit-log entries — who did what to which entity and when. The tool for answering 'who touched this token?'. Basis Theory: GET /logs.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | ISO-8601 upper bound. |
| entity_id | string | – | Only entries for this entity id. |
| entity_type | string | – | Only entries for this entity type, e.g. token, application, proxy. |
| page | integer | – | 1-based page number (offset pagination). |
| size | integer | – | Page size, 1-100. |
| start_date | string | – | ISO-8601 lower bound. |
No output schema declared.
No examples provided.
basis_theory_list_permissions List permissions ~50
List the permissions that can be granted to an application, optionally for one application type. Basis Theory: GET /permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| application_type | string | – | Only permissions valid for this application type. |
No output schema declared.
No examples provided.
basis_theory_list_proxies List proxies ~76
List the proxies that forward requests to third parties, detokenizing in flight. Basis Theory: GET /proxies.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Filter by proxy name. |
| page | integer | – | 1-based page number (offset pagination). |
| size | integer | – | Page size, 1-100. |
No output schema declared.
No examples provided.
basis_theory_list_reactors List reactors ~78
List reactors — the serverless functions that run against detokenized data inside the vault. Basis Theory: GET /reactors.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Filter by reactor name. |
| page | integer | – | 1-based page number (offset pagination). |
| size | integer | – | Page size, 1-100. |
No output schema declared.
No examples provided.
basis_theory_list_roles List roles ~26
List the roles available for tenant members. Basis Theory: GET /roles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
basis_theory_list_tenant_members List tenant members ~66
List the people with access to the tenant, and their roles. Basis Theory: GET /tenants/self/members.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (offset pagination). |
| size | integer | – | Page size, 1-100. |
No output schema declared.
No examples provided.
basis_theory_list_tokens List tokens ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | – | Only tokens in this container path, e.g. /pci/high/. |
| fingerprint | string | – | Only tokens sharing this fingerprint — how you find duplicates of the same card. |
| size | integer | – | Page size, 1-100. |
| start | string | – | Cursor from the previous page's pagination.next. Omit for the first page. |
| type | string | – | Only tokens of this type, e.g. card, bank, token. |
No output schema declared.
No examples provided.
basis_theory_search_tokens Search tokens ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Query string, e.g. type:card AND metadata.customer_id:"cus_1". |
| size | integer | – | Page size, 1-100. |
| start | string | – | Cursor from the previous page's pagination.next. Omit for the first page. |
No output schema declared.
No examples provided.
basis_theory_whoami Identify the configured key ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.usefulapi/basis-theory MCP server?
io.usefulapi/basis-theory is an MCP server listed in the public MCP registry as io.usefulapi/basis-theory. Read token metadata, applications, audit logs, proxies and usage in the PCI vault. This page covers its hosted endpoint (https://basis-theory.usefulapi.io/mcp).
Is the io.usefulapi/basis-theory MCP server safe to use?
io.usefulapi/basis-theory scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/basis-theory MCP server expose?
io.usefulapi/basis-theory exposes 17 tools: basis_theory_list_tokens, basis_theory_search_tokens, basis_theory_get_token, basis_theory_list_applications, basis_theory_get_application, and 12 more. Their descriptions and schemas cost roughly 1,164 tokens of context every time the server is loaded.
Does the io.usefulapi/basis-theory MCP server require authentication?
Yes. io.usefulapi/basis-theory asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/basis-theory MCP server still maintained?
io.usefulapi/basis-theory is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.