Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.
Déduit des transports déclarés par cette annonce (streamable-http). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.
La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.
Lu depuis un véritable échange MCP initialize → tools/list contre l’endpoint déclaré. Aucun outil n’a été invoqué — tools/list est l’appel d’introspection en lecture seule que le protocole prévoit pour cela. Cela reflète ce que le serveur annonçait à cet instant ; un endpoint hébergé n’est figé sur aucune version et peut changer sans préavis.
https://mcp.roki.la/mcp19 outils · 275 msroki_search_docsSearch 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.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ètre | Type | Description |
|---|---|---|
| query* | string | What you need to know, e.g. "webhook signature", "tip fields", "idempotency". |
| limit | integer | Maximum results (default 6). |
roki_get_doc_sectionReturn the complete text of one section of the integration guide, by number (e.g. "14"), sub-number ("12.1") or title fragment ("webhook").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ètre | Type | Description |
|---|---|---|
| ref* | string | Section number, sub-number, or a fragment of its title. |
roki_list_operationsList 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.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.
Aucun schéma d’entrée n’a été publié pour cet outil.
roki_get_operationFull detail for one operation: method, path, headers, request schema field table, responses, and worked examples.Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
| Paramètre | Type | Description |
|---|---|---|
| operation* | string | operationId (e.g. "createPayment"), or "METHOD /path" (e.g. "POST /payments"). |
roki_get_schemaReturn a fully dereferenced JSON Schema by name (e.g. "PaymentCreateRequest", "Payment", "WebhookEvent"). Use it to know the exact field names, types and constraints.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ètre | Type | Description |
|---|---|---|
| name | string | Schema name. Omit to list all available schemas. |
roki_get_errorExplain 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.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ètre | Type | Description |
|---|---|---|
| error* | string | HTTP status ("422"), or a fragment of the message ("Pago no encontrado", "route could not be found", "sandbox"). |
roki_validate_requestValidate 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…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…
| Paramètre | Type | Description |
|---|---|---|
| operation* | string | operationId, e.g. "createPayment". |
| payload* | object | The JSON request body you intend to send. |
roki_check_resultCompare 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 empt…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 empt…
| Paramètre | Type | Description |
|---|---|---|
| sent* | object | The JSON request body you sent to POST /payments. |
| received* | object | The payment object the API returned. Paste the response as-is. |
roki_get_integration_exampleReturn a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.
| Paramètre | Type | Description |
|---|---|---|
| stack | string | e.g. "laravel", "php", "node", "express", "python", "fastapi". Omit to list what is available. |
roki_get_quickstartThe minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.
Aucun schéma d’entrée n’a été publié pour cet outil.
roki_get_authentication_guideHow authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.How authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.
Aucun schéma d’entrée n’a été publié pour cet outil.
roki_get_webhook_guideEverything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback.Everything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback.
Aucun schéma d’entrée n’a été publié pour cet outil.
roki_choose_integration_modeDecide 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 th…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 th…
| Paramètre | Type | Description |
|---|---|---|
| context* | string | What the project is: e.g. "Laravel e-commerce checkout", "iOS app", "card fields on my own page", "invoices from an ERP", "monthly subscriptions". |
roki_verify_webhook_signatureCheck 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 sig…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 sig…
| Paramètre | Type | Description |
|---|---|---|
| raw_body* | string | The EXACT raw request body as received, byte for byte, before any JSON parsing. |
| signature_header* | string | The full ROKI-Signature header value, e.g. "t=1719234300,v1=8f3c..." |
| signing_secret* | string | 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. |
roki_scaffold_integrationReturn 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.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ètre | Type | Description |
|---|---|---|
| stack* | string | e.g. "laravel", "node", "express", "python", "fastapi", "php". |
| mode | string | "hosted" (default), "embedded" or "saved-card". |
roki_audit_integrationReturn 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.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ètre | Type | Description |
|---|---|---|
| focus | string | Optional area: "webhooks", "security", "payments", "reversals". |
roki_sandbox_tryRuns 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 hold…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 hold…
| Paramètre | Type | Description |
|---|---|---|
| operation* | string | operationId to run, e.g. "createPayment", "getPayment", "voidTransaction". |
| payload | object | Request body for POST operations, or path values such as {"id": 123} / {"transaction_id": "uuid"}. |
roki_sandbox_infoWhether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.Whether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.
Aucun schéma d’entrée n’a été publié pour cet outil.
roki_statusServer version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.
Aucun schéma d’entrée n’a été publié pour cet outil.
19 outils sur 19 ont publié une description.
Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.
Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.
Les noms cliquables ouvrent l’index Forge de toutes les entrées observées exposant cet outil. Parcourir tous les outils indexés.
Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.