Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

[mcp_servers.connect]
url = "https://mcp.roki.la/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "connect": {
      "type": "remote",
      "url": "https://mcp.roki.la/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "connect": {
      "type": "http",
      "url": "https://mcp.roki.la/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=connect&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnJva2kubGEvbWNwIn0%3D"
}

{
  "servers": {
    "connect": {
      "type": "http",
      "url": "https://mcp.roki.la/mcp"
    }
  }
}

{
  "mcpServers": {
    "connect": {
      "httpUrl": "https://mcp.roki.la/mcp"
    }
  }
}

extensions:
  "connect":
    enabled: true
    name: "connect"
    type: streamable_http
    uri: "https://mcp.roki.la/mcp"
    timeout: 300

Quality 91 / 100strong

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations19 of 19 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 2,857 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

19 tools, about 2,857 tokens to load them all · tool set 5a595c5d1d59 · checked 2026-10-20 14:54 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 80 / 100

no-repository

provenance55

liveness100

freshness85

hygiene80

+dns-namespace +website +reachable +uptime-100% ~updated-65d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://mcp.roki.la/mcp` streamable-http	none	yes	100%	540 ms	2025-11-25	2026-10-20

Tools (19)

`roki_audit_integration`read-only	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.
`roki_check_result`read-only	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 was wrong. The API answers 201, `warnings` comes back empty because there was nothing to warn about, and the merchant charged something else. Catches the amount off by a factor of 100, fee pass-through asked for and returned as zero, tax that was not applied, `expires_at` already in the past because it was sent as UTC instead of Honduras time, a total that does not add up, and a `transaction_id` parsed as a number. Run it after every createPayment while you are building, and in your own tests afterwards.
`roki_choose_integration_mode`read-only	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 read from the corpus, so this answer cannot describe a mode the API no longer has - or miss one it gained.
`roki_get_authentication_guide`read-only	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`read-only	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`read-only	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.
`roki_get_integration_example`read-only	Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.
`roki_get_operation`read-only	Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
`roki_get_quickstart`read-only	The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.
`roki_get_schema`read-only	Return a fully dereferenced JSON Schema by name (e.g. "PaymentCreateRequest", "Payment", "WebhookEvent"). Use it to know the exact field names, types and constraints.
`roki_get_webhook_guide`read-only	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`read-only	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`read-only	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 payload is valid. You never supply a key: this server holds a sandbox-only credential and refuses to run against production. Amounts are capped and links expire quickly, because the sandbox is shared.
`roki_scaffold_integration`read-only	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.
`roki_search_docs`read-only	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 gateway's conventions.
`roki_status`read-only	Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.
`roki_validate_request`read-only	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 error. The response names what it dropped in `warnings`, but by then the payment exists - validating here means it is never created. Always validate before writing or shipping integration code.
`roki_verify_webhook_signature`read-only	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 whenever webhook verification rejects real events. On the signing secret: this is ROKI's own server and ROKI issued that secret, so sending it here discloses nothing new. It is used to recompute the HMAC and is never stored, logged or counted.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "la.roki/connect",
  "title": "ROKI Connect",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.roki.la/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://mcp.roki.la",
  "description": "Verified ROKI Connect payments contract for coding agents: operations, schemas, validator."
}