Home / MCP registry index / la.roki/connect
ROKI Connect
la.roki/connect in the official MCP registry.
Endpoint https://mcp.roki.la/mcp.
The registry describes it as: Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.
We read its 19 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
roki_search_docs roki_get_doc_section roki_list_operations roki_get_operation roki_get_schema roki_get_error roki_validate_request roki_check_result roki_get_integration_example roki_get_quickstart roki_get_authentication_guide roki_get_webhook_guide roki_choose_integration_mode roki_verify_webhook_signature roki_scaffold_integration roki_audit_integration roki_sandbox_try roki_sandbox_info roki_status
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/la-roki-connect)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.