Home / MCP registry index / io.github.ox31461/robyn

Robyn — Gasless Cross-Chain for AI Agents

io.github.ox31461/robyn in the official MCP registry. Endpoint https://api.anygas.xyz/mcp. Source: github.com/ox31461/Gasless-Anygas-ROBYN-Relay.

The registry describes it as: Gasless cross-chain for AI agents: 25 nodes incl. Solana & native Bitcoin. One signature, no gas.

We read its 87 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http robyn https://api.anygas.xyz/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "robyn": {
      "url": "https://api.anygas.xyz/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"robyn","type":"http","url":"https://api.anygas.xyz/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

robyn_privacy_posture robyn_receipt_deliver robyn_receipt_verify robyn_mesh robyn_quote robyn_settle robyn_attestation robyn_preflight robyn_vip_status robyn_route_status robyn_cross_chain robyn_prepare robyn_sandbox_do robyn_submit robyn_netting_info robyn_netting_account robyn_netting_preview robyn_netting_statement robyn_netting_reserves robyn_netting_enroll_payload robyn_netting_transfer_payload robyn_counterparty_check robyn_preflight_full robyn_integration_lint robyn_recipes robyn_changelog robyn_errors robyn_verify_outcome robyn_plan robyn_spend_statement robyn_fee_forensics robyn_delivery_stats robyn_mandate_events robyn_mandate_list robyn_mandate_cosign_request robyn_mandate_certificate robyn_mandate_check robyn_mandate_status robyn_improve_cost robyn_why_this_route robyn_capability_snapshot robyn_evidence_bundle robyn_payment_request_prepare robyn_payment_request_verify robyn_payment_request_settlement robyn_refusal_verify robyn_7702_delegate robyn_7702_check robyn_sponsor_7702 robyn_yield_account robyn_yield_quote robyn_yield_spend robyn_message_info robyn_message_directory robyn_message_mailbox_of robyn_message_send robyn_message_feed robyn_message_publish_mailbox robyn_plus_info robyn_plus_invoice and 27 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ox31461-robyn/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ox31461-robyn)

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.

Crypto and Web3 MCP servers