API Tools
roki.la
Provides search and retrieval of ROKI Connect API documentation, including operation details, schemas, and integration guide sections.
ENDPOINT 1
https://mcp.roki.la/mcp
MCP server metadata
- Name
- roki-connect
- Version
- 1.0.0
ROKI Connect is a payment gateway in Honduras. This server is the authoritative source for integrating it. RULES: 1. Never invent ROKI endpoints, fields, statuses or error codes. Look them up here first. 2. This API SILENTLY IGNORES unknown fields - a misspelled name returns 201 with the feature off and no warning. Always validate a payload with roki_validate_request before shipping code that sends it. 3. Do not use other gateways' vocabulary (card_token, payment_method, customer_id, amount_cents). Those names are not part of this API and would be silently discarded. 4. Amounts are decimal units (150.50 = L 150.50), never cents. 5. Never hardcode credentials. The secret key is server-side only, read at runtime from configuration. THE API TODAY (ROKI Connect API v2.0.0, corpus verified 2026-08-12): 12 operations - GET /payments, POST /payments, GET /payments/{id}, POST /payments/{transaction_id}/void, POST /payments/{transaction_id}/refund, GET /payments/{transaction_id}/receipt, GET /payments/{transaction_id}/receipt/download, GET /payment-methods, DELETE /payment-methods/{payment_method_id}, POST /payment-methods/{payment_method_id}/charge, POST /payments/token-charge, POST /confirm Void, refund and receipts are keyed by the transaction UUID from the payment response, never by the numeric payment id: passing the payment id yields a routing 404 that looks like a missing endpoint. START HERE: roki_status to check the connection, roki_list_operations to see everything that exists, roki_search_docs for anything else.
Known tools 18
roki_search_docsSearch the official ROKI Connect corpus (integration guide, API operations and schemas) and return ranked excerpts.
Inferred read-onlyroki_get_doc_sectionReturn the complete text of one section of the integration guide, by number (e.
Inferred read-onlyroki_list_operationsList every operation the API actually exposes, plus the operations that are documented as NOT existing.
Inferred read-onlyroki_get_operationFull detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
Inferred read-onlyroki_get_errorExplain an HTTP status or an error message returned by the ROKI API: what it means, the likely cause and what to do.
Potential side effectsroki_validate_requestValidate a payload against the official schema WITHOUT sending it, and check the business rules the API enforces.
Inferred read-onlyroki_get_integration_exampleReturn a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.
Inferred read-onlyroki_get_quickstartThe minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.
Inferred read-onlyroki_get_authentication_guideHow authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.
Inferred read-onlyroki_get_webhook_guideEverything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback.
Inferred read-onlyroki_choose_integration_modeDecide how to integrate ROKI Connect for a given project (web checkout, mobile app, invoice or recurring billing) and get the constraints that apply before writing code.
Potential side effectsroki_verify_webhook_signatureCheck a ROKI-Signature header against the raw body and the signing secret.
Inferred read-onlyroki_scaffold_integrationReturn the full runnable skeleton for a stack: credential storage, API client, checkout flow, webhook handler with signature verification, and the polling fallback.
Inferred read-onlyroki_audit_integrationReturn the checklist to audit existing ROKI code, ordered by how badly each item fails in production.
Inferred read-onlyroki_sandbox_tryRuns a documented operation against the ROKI sandbox using THIS SERVER'S own test credential, and returns the actual response.
Inferred read-onlyroki_sandbox_infoWhether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.roki-connect]
url = "https://mcp.roki.la/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"roki-connect": {
"type": "http",
"url": "https://mcp.roki.la/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: roki-connect
Remote MCP URL: https://mcp.roki.la/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"roki-connect": {
"url": "https://mcp.roki.la/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"roki-connect": {
"type": "http",
"url": "https://mcp.roki.la/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "roki-connect",
"transport": "streamable-http",
"url": "https://mcp.roki.la/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for roki.la was fetched 2026-08-18T07:33:35.704Z.
roki.la is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.