ROKI Connect

Name: ROKI Connect
Author: la.roki

MCP serverMCP

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

by la.rokihomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"roki-connect","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availabilityno checks in window

30 days agotoday

Tools observed via MCP handshake

roki_search_docs — Search the official ROKI Connect corpus (integration guide, API operations and schemas) and return ranked excerpts. Use this first when you need any ROKI-specif
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 integration code so you nev
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 names, types and constr
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 guessing when an integr
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 ignores unknown fiel
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 what you SEND. This one
roki_get_integration_example — Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling
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 processing, and the pollin
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 get the constraints
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 specific wrong constru
roki_scaffold_integration — Return the full runnable skeleton for a stack: credential storage, API client, checkout flow, webhook handler with signature verification, and the polling fallb
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 you did not write, or
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 prove an integration wo
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.

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryla.roki/connect

first seen 9 h ago · fetched 9 h agoopen ↗

Field history (6 recent events)

9 h ago · declared · summary → "Verified ROKI Connect payments contract for coding agents: operations, schemas, validator."
9 h ago · declared · description → "Verified ROKI Connect payments contract for coding agents: operations, schemas, validator."
9 h ago · declared · publisherName → "la.roki"
9 h ago · declared · homepageUrl → "https://mcp.roki.la"
9 h ago · declared · version → "1.0.0"
9 h ago · declared · protocols → ["mcp"]

when	check	result	http	latency	detail
22 min ago	mcp initialize	ok	200	91 ms	server roki-connect 1.0.0 · protocol 2025-06-18 · 19 tools
8 h ago	mcp initialize	ok	200	92 ms	server roki-connect 1.0.0 · protocol 2025-06-18 · 19 tools

ROKI Connect

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from