Basis Theory MCP by usefulapi

Each tool maps to a distinct resource+action: get_* for single entities, list_* for collections, plus clearly separated search_tokens and whoami. The get_token vs list_tokens vs search_tokens trio is well-differentiated by explicit metadata-only and warning language. No meaningful overlap remains.

All tools follow a uniform namespace_pattern of basis_theory_<verb>_<noun> (get_*, list_*, search_*, whoami). The convention is applied without deviation across all 17 tools, making intent predictable.

17 tools is slightly above the ideal 3-15 band, but each one maps to a concrete Basis Theory endpoint and earns its place. No redundant or filler tools are present, so the count is reasonable for the breadth of resources covered.

The surface is deliberately read-only and covers the main read domains (applications, proxies, reactors, tenants, tokens, logs, roles, permissions, members) thoroughly. However, no create/update/delete operations exist for any resource, so an agent cannot perform lifecycle changes on applications, tokens, proxies, or reactors.