Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Robyn — Gasless Cross-Chain for AI Agents

NPM · ANYGAS-MCP · 2 COMPONENTS · SCANNED SEP 20

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

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 404 tokens (~101/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "robyn_cross_chain" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Robyn — Gasless Cross-Chain for AI Agents MCP server?

Robyn — Gasless Cross-Chain for AI Agents runs locally as an npm package, launched with npx -y anygas-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · anygas-mcp

# add to Claude Code
claude mcp add ox31461-robyn -- npx -y anygas-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ox31461-robyn": {
      "command": "npx",
      "args": [
        "-y",
        "anygas-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ox31461-robyn": {
      "command": "npx",
      "args": [
        "-y",
        "anygas-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ox31461-robyn -- npx -y anygas-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ox31461-robyn": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "anygas-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ox31461-robyn --command npx --arg -y --arg anygas-mcp
# ~/.hermes/config.yaml
mcp_servers:
  ox31461-robyn:
    command: "npx"
    args: ["-y", "anygas-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ox31461-robyn": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "anygas-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ox31461-robyn -t stdio -c npx -a -y anygas-mcp
// mcp.json
{
  "mcpServers": {
    "ox31461-robyn": {
      "command": "npx",
      "args": [
        "-y",
        "anygas-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 12 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/anygas-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 105 packages
Packages resolved 105
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~404 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
robyn_cross_chain ~164

Execute a gasless cross-chain move: the server signs ONE Permit2 intent and Robyn fronts all native gas on both chains + the bridge, reimbursed from the token. The agent pays no gas and signs nothing else. Requires ROBYN_SIGNER_KEY in the server env, and a one-time Permit2 approval of the token. Returns a route id — track it with robyn_route_status.

NameTypeReqDescription
amountstringyesamount in fromToken base units
fromChainnumber|stringyes
fromTokenstringyestoken address on the source chain
toAddressstringrecipient (defaults to the signer)
toChainnumber|stringyes
toTokenstringyestoken address / symbol on the destination

No output schema declared.

No examples provided.

robyn_mesh ~43

List the Robyn gasless chains and the cross-chain route graph (22 EVM nodes + Stellar), plus the relayer/Permit2 addresses. No credentials needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

robyn_quote ~158

Best gasless route to move a token from one Robyn chain to another. Returns estimated output, the bridge used, duration, and the Robyn fee. Read-only — moves nothing.

NameTypeReqDescription
amountstringyesamount in fromToken base units (e.g. "25000000" = 25 USDC)
fromChainnumber|stringyessource chain id, or "stellar"
fromTokenstringyestoken address on the source chain (0x0000…0000 for native)
toAddressstringrecipient on the destination chain
toChainnumber|stringyesdestination chain id, or "stellar"
toTokenstringyestoken address / symbol on the destination

No output schema declared.

No examples provided.

robyn_route_status ~39

Status of an in-flight route by id (BRIDGING → DONE), with the destination tx once delivered.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

Common questions

What is the Robyn — Gasless Cross-Chain for AI Agents MCP server?

Robyn — Gasless Cross-Chain for AI Agents is an MCP server listed in the public MCP registry as io.github.ox31461/robyn. Gasless cross-chain for AI agents: 25 nodes incl. Solana & native Bitcoin. One signature, no gas. This page covers its npm package (anygas-mcp).

Is the Robyn — Gasless Cross-Chain for AI Agents MCP server safe to use?

Robyn — Gasless Cross-Chain for AI Agents scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Robyn — Gasless Cross-Chain for AI Agents MCP server expose?

Robyn — Gasless Cross-Chain for AI Agents exposes 4 tools: robyn_mesh, robyn_quote, robyn_route_status, robyn_cross_chain. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.

Is the Robyn — Gasless Cross-Chain for AI Agents MCP server still maintained?

Robyn — Gasless Cross-Chain for AI Agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Robyn — Gasless Cross-Chain for AI Agents MCP server under?

Robyn — Gasless Cross-Chain for AI Agents declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.