Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
ROKI Connect is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
19
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http roki-connect-mcp https://mcp.roki.la/mcp
# 2 — ask your agent for something these tools do
# roki_search_docs, roki_get_doc_section, roki_list_operations and 16 more
ROKI Connect costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ROAll 1 server
roki1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http roki-connect-mcp https://mcp.roki.la/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What you need to know, e.g. "webhook signature", "tip fields", "idempotency". |
| limit | integer | no | Maximum results (default 6). |
Return the complete text of one section of the integration guide, by number (e.g. "14"), sub-number ("12.1") or title fragment ("webhook").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | Section number, sub-number, or a fragment of its title. |
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.
No parameter schema on file.
Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | operationId (e.g. "createPayment"), or "METHOD /path" (e.g. "POST /payments"). |
Return a fully dereferenced JSON Schema by name (e.g. "PaymentCreateRequest", "Payment", "WebhookEvent"). Use it to know the exact field names, types and constraints.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Schema name. Omit to list all available schemas. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| error | string | yes | HTTP status ("422"), or a fragment of the message ("Pago no encontrado", "route could not be found", "sandbox"). |
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 writin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | operationId, e.g. "createPayment". |
| payload | object | yes | The JSON request body you intend to send. |
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 amoun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sent | object | yes | The JSON request body you sent to POST /payments. |
| received | object | yes | The payment object the API returned. Paste the response as-is. |
Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stack | string | no | e.g. "laravel", "php", "node", "express", "python", "fastapi". Omit to list what is available. |
The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.
No parameter schema on file.
How authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.
No parameter schema on file.
Everything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | string | yes | What the project is: e.g. "Laravel e-commerce checkout", "iOS app", "card fields on my own page", "invoices from an ERP", "monthly subscriptions". |
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 noth
| Parameter | Type | Required | Notes |
|---|---|---|---|
| raw_body | string | yes | The EXACT raw request body as received, byte for byte, before any JSON parsing. |
| signature_header | string | yes | The full ROKI-Signature header value, e.g. "t=1719234300,v1=8f3c..." |
| signing_secret | string | yes | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stack | string | yes | e.g. "laravel", "node", "express", "python", "fastapi", "php". |
| mode | string | no | "hosted" (default), "embedded" or "saved-card". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| focus | string | no | Optional area: "webhooks", "security", "payments", "reversals". |
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 expir
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | operationId to run, e.g. "createPayment", "getPayment", "voidTransaction". |
| payload | object | no | Request body for POST operations, or path values such as {"id": 123} / {"transaction_id": "uuid"}. |
Whether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.
No parameter schema on file.
Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ROKI Connect or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ROKI Connect can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.