KitScout

Categories › Business & Finance › Payments & billing

ROKI Connect

MCP serverVerified domain · roki.laRemote● LiveFree to try

Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.

Install

Remote server: your requests and data go to mcp.roki.la. Claude Code: claude mcp add --transport http roki-connect https://mcp.roki.la/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

  • roki_search_docs — Search the official ROKI Connect corpus (integration guide, API operations and schemas) and return ranked excerpts. Use this first when you
  • roki_get_doc_section — Return the complete text of one section of the integration guide, by number (e.g. "14"), sub-number ("12.1") or title fragment ("webhook").
  • roki_list_operations — List every operation the API actually exposes, plus the operations that are documented as NOT existing. Call this before writing any integra
  • roki_get_operation — Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
  • roki_get_schema — Return a fully dereferenced JSON Schema by name (e.g. "PaymentCreateRequest", "Payment", "WebhookEvent"). Use it to know the exact field nam
  • roki_get_error — Explain an HTTP status or an error message returned by the ROKI API: what it means, the likely cause and what to do. Use this instead of gue
  • roki_validate_request — Validate a payload against the official schema WITHOUT sending it, and check the business rules the API enforces. Critical for this API: it
  • roki_check_result — Compare the payment the API returned against the body you sent, and report anything that does not match. Every other check here looks at wha
  • roki_get_integration_example — Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verifi
  • roki_get_quickstart — The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.
  • roki_get_authentication_guide — How authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.
  • roki_get_webhook_guide — Everything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent proces
  • roki_choose_integration_mode — Decide how to integrate ROKI Connect for a given project (web checkout, embedded card fields, mobile app, invoices or recurring billing) and
  • roki_verify_webhook_signature — Check a ROKI-Signature header against the raw body and the signing secret. When it fails, this does not just say "invalid" - it tries the sp
  • roki_scaffold_integration — Return the full runnable skeleton for a stack: credential storage, API client, checkout flow, webhook handler with signature verification, a
  • roki_audit_integration — Return the checklist to audit existing ROKI code, ordered by how badly each item fails in production. Use it when reviewing an integration y
  • roki_sandbox_try — Runs a documented operation against the ROKI sandbox using THIS SERVER'S own test credential, and returns the actual response. Use it to pro
  • roki_sandbox_info — Whether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.
  • roki_status — Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools