Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Basis Theory MCP by usefulapi

REMOTE · BASIS-THEORY.USEFULAPI.IO

Read token metadata, applications, audit logs, proxies and usage in the PCI vault.

0 this week 18 Trust /100

Last scanned (16 hours ago)

Scores higher than 3% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Nov 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “check_the_proxies_and_reactors_you_run” functional
    • New prompt “check_token_counts_and_api_usage” functional
    • New prompt “find_out_who_changed_things_in_the_vault” functional
    • New prompt “find_the_tokens_that_belong_to_a_customer” functional
    • New prompt “review_who_has_access_to_the_account” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 +1
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 0
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 +1
    • Server version: 1.24.0 → 1.25.0 functional
  • 25 Oct 26 +1
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
Diagnostics

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 21 Nov 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 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 93e2fea3bbc31354138c8a47c5e87592
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. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

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 Redirected 302 https://usefulapi.io/basis-theory/
http (plaintext) http://basis-theory.usefulapi.io/mcp Inconclusive 302 http://basis-theory.usefulapi.io/mcp
MCP tools · 17 exposed · ~1,164 tokens

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 →

Tool Tokens
basis_theory_get_application ~42

Fetch a single application with its type and permission list. Basis Theory: GET /applications/{id}.

NameTypeReqDescription
application_idstringyesThe application's id.

No output schema declared.

No examples provided.

basis_theory_get_proxy ~45

Fetch a single proxy with its destination URL and transform configuration. Basis Theory: GET /proxies/{id}.

NameTypeReqDescription
proxy_idstringyesThe proxy's id.

No output schema declared.

No examples provided.

basis_theory_get_reactor ~42

Fetch a single reactor with its configuration. Basis Theory: GET /reactors/{id}.

NameTypeReqDescription
reactor_idstringyesThe reactor's id.

No output schema declared.

No examples provided.

basis_theory_get_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 ~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 ~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}.

NameTypeReqDescription
token_idstringyesThe token's id.

No output schema declared.

No examples provided.

basis_theory_list_applications ~90

List the applications (API-key holders) in the tenant, with their types and permissions. Basis Theory: GET /applications.

NameTypeReqDescription
pageinteger–1-based page number (offset pagination).
sizeinteger–Page size, 1-100.
typestring–Only applications of this type, e.g. private, public, management, expiring.

No output schema declared.

No examples provided.

basis_theory_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 ~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.

NameTypeReqDescription
end_datestring–ISO-8601 upper bound.
entity_idstring–Only entries for this entity id.
entity_typestring–Only entries for this entity type, e.g. token, application, proxy.
pageinteger–1-based page number (offset pagination).
sizeinteger–Page size, 1-100.
start_datestring–ISO-8601 lower bound.

No output schema declared.

No examples provided.

basis_theory_list_permissions ~50

List the permissions that can be granted to an application, optionally for one application type. Basis Theory: GET /permissions.

NameTypeReqDescription
application_typestring–Only permissions valid for this application type.

No output schema declared.

No examples provided.

basis_theory_list_proxies ~76

List the proxies that forward requests to third parties, detokenizing in flight. Basis Theory: GET /proxies.

NameTypeReqDescription
namestring–Filter by proxy name.
pageinteger–1-based page number (offset pagination).
sizeinteger–Page size, 1-100.

No output schema declared.

No examples provided.

basis_theory_list_reactors ~78

List reactors — the serverless functions that run against detokenized data inside the vault. Basis Theory: GET /reactors.

NameTypeReqDescription
namestring–Filter by reactor name.
pageinteger–1-based page number (offset pagination).
sizeinteger–Page size, 1-100.

No output schema declared.

No examples provided.

basis_theory_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 ~66

List the people with access to the tenant, and their roles. Basis Theory: GET /tenants/self/members.

NameTypeReqDescription
pageinteger–1-based page number (offset pagination).
sizeinteger–Page size, 1-100.

No output schema declared.

No examples provided.

basis_theory_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.

NameTypeReqDescription
containerstring–Only tokens in this container path, e.g. /pci/high/.
fingerprintstring–Only tokens sharing this fingerprint — how you find duplicates of the same card.
sizeinteger–Page size, 1-100.
startstring–Cursor from the previous page's pagination.next. Omit for the first page.
typestring–Only tokens of this type, e.g. card, bank, token.

No output schema declared.

No examples provided.

basis_theory_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.

NameTypeReqDescription
querystringyesQuery string, e.g. type:card AND metadata.customer_id:"cus_1".
sizeinteger–Page size, 1-100.
startstring–Cursor from the previous page's pagination.next. Omit for the first page.

No output schema declared.

No examples provided.

basis_theory_whoami ~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.

Install

How do I install the Basis Theory MCP by usefulapi server?

Basis Theory MCP by usefulapi 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

# add to Claude Code
claude mcp add --transport http io-usefulapi-basis-theory 'https://basis-theory.usefulapi.io/mcp'
Common questions

What is the Basis Theory MCP by usefulapi server?

Basis Theory MCP by usefulapi is 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 Basis Theory MCP by usefulapi server safe to use?

Basis Theory MCP by usefulapi scores 18 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 Basis Theory MCP by usefulapi server expose?

Basis Theory MCP by usefulapi 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 Basis Theory MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Basis Theory MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Basis Theory MCP by usefulapi server still maintained?

Basis Theory MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Basis Theory MCP by usefulapi server?

VerifyMCP ran 4 checks on Basis Theory MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Basis Theory MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.