Developer Tools

tokenz.one

Search and retrieve Tokenz API documentation, including OpenAPI specs and test card information.

1 endpoint14 known toolsFirst detected May 29, 2026Last detected August 6, 2026

ENDPOINT 1

https://mcp.tokenz.one/mcp

No auth detected

MCP server metadata

Name: tokenz
Version: 2.0.5

Capabilities

tools.listChanged

Server instructions

Tokenz MCP — helps you integrate Tokenz (a Merchant of Record checkout). Two tiers of tools: - Docs (no auth): search_docs, get_doc, list_docs, get_openapi, list_test_cards — the live Tokenz documentation, API reference, and test cards. Start here. - Test actions (need a secret_test_ key on the connection): create_test_checkout_session, get_checkout_session, get_order, cancel_test_order, create_test_refund, get_refund, and verify_webhook_signature. Build and verify a full integration in TEST mode. A live key is refused — these never touch real money. Typical flow: search_docs → build the integration → create_test_checkout_session → open the URL, pay with 4242 4242 4242 4242 (list_test_cards) → get_order to confirm → test refunds/webhooks (create_test_refund, verify_webhook_signature).

Known tools 14

search_docs

Search the live Tokenz docs (guides + API reference) and return the most relevant pages with snippets and links.

Inferred read-only

get_doc

Fetch the full clean Markdown for a documentation page by its path, e.g.

Inferred read-only

list_docs

List every documentation page (title, description, path) so you can pick what to read.

Inferred read-only

list_test_cards

Return the test card numbers and how to force success/decline in test mode.

Inferred read-only

get_openapi

Return the OpenAPI (v2) spec for a Tokenz API service.

Inferred read-only

verify_webhook_signature

Check a `Tokenz-Signature` header against the raw request body using the endpoint signing secret.

Inferred read-only

sign_test_webhook_payload

Produce a correctly-signed Tokenz webhook request so you can test your webhook handler locally BEFORE any real purchase or tunnel — the counterpart to verify_webhook_signature.

Potential side effects

check_auth

Diagnose the MCP connection before (or after a failure with) the test-action tools: whether a key was detected on the connection, whether it is a test key, whether test actions are enabled, and whether the key actually authenticates against the Tokenz API.

Inferred read-only

create_test_checkout_session

Create a Tokenz TEST-mode Checkout Session and return the hosted checkout URL.

Potential side effects

get_checkout_session

Fetch a Checkout Session by ID to inspect its status and hosted URL.

Inferred read-only

get_order

Fetch an order by ID to check its status after a test checkout.

Inferred read-only

cancel_test_order

Cancel an unpaid/pending TEST order to exercise the cancellation path.

Inferred read-only

create_test_refund

Fully refund a paid TEST order so you can build and verify your refund + webhook handling.

Potential side effects

get_refund

Fetch a refund by ID to check its status.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tokenz]
url = "https://mcp.tokenz.one/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tokenz": {
      "type": "http",
      "url": "https://mcp.tokenz.one/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tokenz
Remote MCP URL: https://mcp.tokenz.one/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tokenz": {
      "url": "https://mcp.tokenz.one/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tokenz": {
      "type": "http",
      "url": "https://mcp.tokenz.one/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tokenz",
  "transport": "streamable-http",
  "url": "https://mcp.tokenz.one/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.