# Roki Connect MCP server

Source: https://glimind.com/server/mcp-registry%2Fla.roki%2Fconnect
Registry id: `mcp-registry/la.roki/connect`
Status: live (checked 2026-10-27T14:10:58.455Z)

## Verdict

Roki Connect MCP server answered 99.96% of Glimind's liveness checks over 30 days, better than 36% of MCP servers, with 899 ms median handshake and 3 outages in 90 days. Its agent-readiness grade is A (96/100) across 19 tools, costing an agent about 2,877 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.96% | 36% of MCP servers |
| Median handshake latency | 899 ms | 19% of MCP servers |
| p95 handshake latency | 3216 ms | — |
| Checks in 30 days | 5,078 | — |
| Outages, 90 days | 3 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 19 | — |
| Tool-list size for an agent | ~2,877 tokens | 46% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "roki-connect-mcp-server": {
      "type": "http",
      "url": "https://mcp.roki.la/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http roki-connect-mcp-server https://mcp.roki.la/mcp
```

## Tools (19)

- `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_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_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_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").
- `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_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_operation`: Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
- `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 constr
- `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_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_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 wo
- `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_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_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 fiel
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.