Connect ROKI Connect and your agent gets 19 tools, among them roki_audit_integration, roki_check_result, roki_choose_integration_mode. It answers at https://mcp.roki.la/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 before going live. Inputs: focus |
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 exists for the errors that survive that: the field name was right and the VALUE Inputs: sent, received |
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 that apply before writing code. The modes and the endpoints behind them are rea Inputs: context |
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_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"). Inputs: ref |
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 integration fails. Inputs: error |
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 fallback. Inputs: stack |
roki_get_operation | Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples. Inputs: operation |
roki_get_quickstart | The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip. |
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 constraints. Inputs: name |
roki_get_webhook_guide | Everything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback. |
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 never invent an endpoint. |
roki_sandbox_info | Whether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards. |
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 works instead of assuming it does - especially after roki_validate_request says a Inputs: operation, payload |
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 fallback. Use it to start an integration instead of assembling one from memory. Inputs: stack, mode |
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-specific fact. Never answer a ROKI question from memory or from another payment gatewa Inputs: query, limit |
roki_status | Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data. |
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 fields and returns 201, so a typo produces a misconfigured payment rather than an er Inputs: operation, payload |
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 constructions developers actually write and tells you which mistake you made. Use it wh Inputs: raw_body, signature_header, signing_secret |
Every block below points at https://mcp.roki.la/mcp. Pick your client and copy.
claude mcp add --transport http roki-connect https://mcp.roki.la/mcp
{
"mcpServers": {
"roki-connect": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.roki.la/mcp"]
}
}
}{
"mcpServers": {
"roki-connect": {
"url": "https://mcp.roki.la/mcp"
}
}
}{
"servers": {
"roki-connect": {
"type": "http",
"url": "https://mcp.roki.la/mcp"
}
}
}{
"context_servers": {
"roki-connect": {
"url": "https://mcp.roki.la/mcp"
}
}
}{
"mcpServers": {
"roki-connect": {
"serverUrl": "https://mcp.roki.la/mcp"
}
}
}{
"mcpServers": {
"roki-connect": {
"url": "https://mcp.roki.la/mcp"
}
}
}name: ROKI Connect
version: 0.0.1
schema: v1
mcpServers:
- name: ROKI Connect
type: streamable-http
url: https://mcp.roki.la/mcp{
"mcpServers": {
"roki-connect": {
"httpUrl": "https://mcp.roki.la/mcp"
}
}
}{
"mcpServers": {
"roki-connect": {
"type": "http",
"url": "https://mcp.roki.la/mcp"
}
}
}{
"mcpServers": {
"roki-connect": {
"url": "https://mcp.roki.la/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.roki.la%2Fmcp&type=streamable_http&id=roki-connect&name=ROKI%20Connect
It answered our last check on 24 October 2026 in 473 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by roki.la and served from mcp.roki.la, the vendor's own domain: https://mcp.roki.la/mcp.
19, as returned by the server's own tools/list on 22 September 2026: roki_audit_integration, roki_check_result, roki_choose_integration_mode, roki_get_authentication_guide, roki_get_doc_section, roki_get_error, roki_get_integration_example, roki_get_operation, and 11 more.
It answered our last check on 24 October 2026 in 473 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.roki.la/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: la.roki. Endpoint host: mcp.roki.la. ARD identifier: urn:air:la.roki:mcp:connect.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.