la.roki/connect

Est-ce que la.roki/connect est sûr ?

Au dernier audit MCP Hub, le serveur MCP « la.roki/connect » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 19 outils

• roki_audit_integration≈ 160 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • focus · string · optionnel
    Optional area: "webhooks", "security", "payments", "reversals".

  Exemple d'appel

  {"name": "roki_audit_integration", "arguments": {"focus": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_check_result≈ 367 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • sent · object · requis
    The JSON request body you sent to POST /payments.
  • received · object · requis
    The payment object the API returned. Paste the response as-is.

  Exemple d'appel

  {"name": "roki_check_result", "arguments": {"sent": {}, "received": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_choose_integration_mode≈ 226 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • context · string · requis
    What the project is: e.g. "Laravel e-commerce checkout", "iOS app", "card fields on my own page", "invoices from an ERP", "monthly subscriptions".

  Exemple d'appel

  {"name": "roki_choose_integration_mode", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_authentication_guide≈ 118 tokens

  How authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "roki_get_authentication_guide", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_doc_section≈ 147 tokens

  Return the complete text of one section of the integration guide, by number (e.g. "14"), sub-number ("12.1") or title fragment ("webhook").

  Paramètres, retour & exemple (1)

  Paramètres

  • ref · string · requis
    Section number, sub-number, or a fragment of its title.

  Exemple d'appel

  {"name": "roki_get_doc_section", "arguments": {"ref": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_error≈ 167 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • error · string · requis
    HTTP status ("422"), or a fragment of the message ("Pago no encontrado", "route could not be found", "sandbox").

  Exemple d'appel

  {"name": "roki_get_error", "arguments": {"error": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_integration_example≈ 165 tokens

  Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.

  Paramètres, retour & exemple (1)

  Paramètres

  • stack · string · optionnel
    e.g. "laravel", "php", "node", "express", "python", "fastapi". Omit to list what is available.

  Exemple d'appel

  {"name": "roki_get_integration_example", "arguments": {"stack": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_operation≈ 149 tokens

  Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.

  Paramètres, retour & exemple (1)

  Paramètres

  • operation · string · requis
    operationId (e.g. "createPayment"), or "METHOD /path" (e.g. "POST /payments").

  Exemple d'appel

  {"name": "roki_get_operation", "arguments": {"operation": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_quickstart≈ 104 tokens

  The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "roki_get_quickstart", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_schema≈ 142 tokens

  Return a fully dereferenced JSON Schema by name (e.g. "PaymentCreateRequest", "Payment", "WebhookEvent"). Use it to know the exact field names, types and constraints.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · optionnel
    Schema name. Omit to list all available schemas.

  Exemple d'appel

  {"name": "roki_get_schema", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_get_webhook_guide≈ 120 tokens

  Everything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "roki_get_webhook_guide", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_list_operations≈ 124 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "roki_list_operations", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_sandbox_info≈ 108 tokens

  Whether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "roki_sandbox_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_sandbox_try≈ 293 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • payload · object · optionnel
    Request body for POST operations, or path values such as {"id": 123} / {"transaction_id": "uuid"}.
  • operation · string · requis
    operationId to run, e.g. "createPayment", "getPayment", "voidTransaction".

  Exemple d'appel

  {"name": "roki_sandbox_try", "arguments": {"operation": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_scaffold_integration≈ 202 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • mode · string · optionnel
    "hosted" (default), "embedded" or "saved-card".
  • stack · string · requis
    e.g. "laravel", "node", "express", "python", "fastapi", "php".

  Exemple d'appel

  {"name": "roki_scaffold_integration", "arguments": {"stack": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_search_docs≈ 211 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Maximum results (default 6).
  • query · string · requis
    What you need to know, e.g. "webhook signature", "tip fields", "idempotency".

  Exemple d'appel

  {"name": "roki_search_docs", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_status≈ 111 tokens

  Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "roki_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_validate_request≈ 259 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • payload · object · requis
    The JSON request body you intend to send.
  • operation · string · requis
    operationId, e.g. "createPayment".

  Exemple d'appel

  {"name": "roki_validate_request", "arguments": {"payload": {}, "operation": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• roki_verify_webhook_signature≈ 343 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • raw_body · string · requis
    The EXACT raw request body as received, byte for byte, before any JSON parsing.
  • signing_secret · string · requis
    The signing secret from the portal, for the same environment as the event. Held in memory for the duration of the call only: this server logs no tool arguments.
  • signature_header · string · requis
    The full ROKI-Signature header value, e.g. "t=1719234300,v1=8f3c..."

  Exemple d'appel

  {"name": "roki_verify_webhook_signature", "arguments": {"raw_body": "texte", "signing_secret": "texte", "signature_header": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.roki.la/mcp