ROKI Connect MCP server
la.roki/connectroki.lastreamable-httpv1.0.0Scanned
Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.
19 tools: 4 change things and 15 only read.
- Reads private data · 6
- Reads text others write · 2
- Can send data out · 0
- 5 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ROKI Connect MCP server can do
The ROKI Connect MCP server is published by roki.la, a domain the MCP Registry verified. It has 19 tools. It can create or change data (4 tools: roki_choose_integration_mode, roki_verify_webhook_signature, roki_sandbox_try and roki_sandbox_info), but cannot delete data. 15 tools only read.
6 tools read private data (roki_search_docs, roki_get_doc_section, roki_get_operation and 3 more); 2 tools bring in text other people can write (roki_get_error and roki_sandbox_try).
The fixed checks matched 5 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
19 tools
Changes things 4Claude Code: ask
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 w…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_sandbox_infoWhether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Whether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_sandbox_tryRuns a documented operation against the ROKI sandbox using THIS SERVER'S own test credential, and returns the actual response.Reads text others write1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...KI sandbox using THIS SERVER'S own test credential, and returns the actual response. Use i..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
roki_verify_webhook_signatureCheck a ROKI-Signature header against the raw body and the signing secret.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 15Show 15 read-only tools
roki_audit_integrationReturn the checklist to audit existing ROKI code, ordered by how badly each item fails in production.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_check_resultCompare the payment the API returned against the body you sent, and report anything that does not match.No findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_get_authentication_guideHow authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.Reads private data2 findings
Why it is in this group
- The name "roki_get_authentication_guide" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "credential": it reads secrets.
Findings
- Info
The title mentions "credentials".
What this check looks forMatched text
title: "ROKI Connect authentication and credentials"
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...he two environments are selected, where credentials come from, and how to store and rotate..."
Description, as the server wrote it How authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_get_doc_sectionReturn the complete text of one section of the integration guide, by number (e.g.Reads private dataNo findings
Why it is in this group
- The name "roki_get_doc_section" says "get": a word for reading.
What it can reach
- private-dataThe name "roki_get_doc_section" says "get" and "doc": it reads documents.
Description, as the server wrote it Return the complete text of one section of the integration guide, by number (e.g. "14"), sub-number ("12.1") or title fragment ("webhook").
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "roki_get_error" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "explain" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "explain" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- The name "roki_get_integration_example" says "get": a word for reading.
Description, as the server wrote it Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_get_operationFull detail for one operation: method, path, headers, request schema field table, responses, and worked examples.Reads private dataNo findings
Why it is in this group
- The name "roki_get_operation" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_get_quickstartThe minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.No findings
Why it is in this group
- The name "roki_get_quickstart" says "get": a word for reading.
Description, as the server wrote it The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_get_schemaReturn a fully dereferenced JSON Schema by name (e.g.No findings
Why it is in this group
- The name "roki_get_schema" says "get": a word for reading.
Description, as the server wrote it Return a fully dereferenced JSON Schema by name (e.g. "PaymentCreateRequest", "Payment", "WebhookEvent"). Use it to know the exact field names, types and constraints.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- The name "roki_get_webhook_guide" says "get": a word for reading.
Description, as the server wrote it Everything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_list_operationsList every operation the API actually exposes, plus the operations that are documented as NOT existing.No findings
Why it is in this group
- The name "roki_list_operations" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.Reads private data1 finding
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "credential": it reads secrets.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...the full runnable skeleton for a stack: credential storage, API client, checkout flow, web..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_search_docsSearch the official ROKI Connect corpus (integration guide, API operations and schemas) and return ranked excerpts.Reads private dataNo findings
Why it is in this group
- The name "roki_search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "roki_search_docs" says "search" and "doc": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_statusServer version, corpus contents and freshness.1 finding
Why it is in this group
- The name "roki_status" says "status": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...onfirm the connection works. Exposes no credentials and no merchant data."
Description, as the server wrote it Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roki_validate_requestValidate a payload against the official schema WITHOUT sending it, and check the business rules the API enforces.No findings
Why it is in this group
- The name "roki_validate_request" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data6
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.roki.la/mcp: tools/list returned 19 tools to an anonymous client, including roki_choose_integration_mode (write), roki_verify_webhook_signature (write), roki_sandbox_try (write), roki_sandbox_info (write)
Findings
Matches of fixed checks, with the text they matched.
The title mentions "credentials".
What this check looks forMatched text
title: "ROKI Connect authentication and credentials"
The description mentions "credentials".
What this check looks forMatched text
description: "...he two environments are selected, where credentials come from, and how to store and rotate..."
The description mentions "credential".
What this check looks forMatched text
description: "...the full runnable skeleton for a stack: credential storage, API client, checkout flow, web..."
- Inforoki_sandbox_try
The description mentions "credential".
What this check looks forMatched text
description: "...KI sandbox using THIS SERVER'S own test credential, and returns the actual response. Use i..."
- Inforoki_status
The description mentions "credentials".
What this check looks forMatched text
description: "...onfirm the connection works. Exposes no credentials and no merchant data."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http connect https://mcp.roki.la/mcpclaude mcp add --transport http connect https://mcp.roki.la/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__connect__roki_search_docs",
"mcp__connect__roki_get_doc_section",
"mcp__connect__roki_list_operations",
"mcp__connect__roki_get_operation",
"mcp__connect__roki_get_schema",
"mcp__connect__roki_get_error",
"mcp__connect__roki_validate_request",
"mcp__connect__roki_check_result",
"mcp__connect__roki_get_integration_example",
"mcp__connect__roki_get_quickstart",
"mcp__connect__roki_get_authentication_guide",
"mcp__connect__roki_get_webhook_guide",
"mcp__connect__roki_scaffold_integration",
"mcp__connect__roki_audit_integration",
"mcp__connect__roki_status"
],
"ask": [
"mcp__connect__roki_choose_integration_mode",
"mcp__connect__roki_verify_webhook_signature",
"mcp__connect__roki_sandbox_try",
"mcp__connect__roki_sandbox_info"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as connect. Review it before you use it.
Capability tags behind 7 rules
- mcp__connect__roki_search_docs private-data
- mcp__connect__roki_get_doc_section private-data
- mcp__connect__roki_get_operation private-data
- mcp__connect__roki_get_error private-data, untrusted-input
- mcp__connect__roki_get_authentication_guide private-data
- mcp__connect__roki_scaffold_integration private-data
- mcp__connect__roki_sandbox_try untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/la.roki/connect/verify?hash=bc206173a5b9a1d5082ef39283dc60bf1aadae1d0a1af96208f5283030bb549e" | jq -e '.changed == false'Pinned hash bc206173a5b9, from Nov 18, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/la.roki/connect/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/la.roki/connect)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
ROKI Connect MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ROKI Connect MCP server safe?
- No scan can promise that. What its definitions show: 19 tools, 4 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ROKI Connect MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ROKI Connect MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ROKI Connect MCP server have?
- 19 tools: 4 write, 15 read. roki_choose_integration_mode, roki_verify_webhook_signature, roki_sandbox_try, roki_sandbox_info, roki_search_docs, roki_get_doc_section, roki_list_operations, roki_get_operation and 11 more.
Does the ROKI Connect MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ROKI Connect MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ROKI Connect MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.