mcp-registry/io.github.ox31461/robyn · v1.6.0
As of 2026-10-20 02:06 UTC, the Ox31461 Robyn MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 38 outages in 90 days, with a median recovery of 2 minutes.
Gasless cross-chain for AI agents: 25 nodes incl. Solana & native Bitcoin. One signature, no gas.
Claude Code
claude mcp add --transport http ox31461-robyn-mcp-server https://api.anygas.xyz/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ox31461-robyn-mcp-server": {
"type": "http",
"url": "https://api.anygas.xyz/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
87 of 87 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
87 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
33 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
79 parameter(s) across 30 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~17,954 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~2,333 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 30 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ox31461%2Frobyn/fixes
{
"name": "null_balance",
"description": "Reads an address balance through the NULL server-side RPC proxy, so YOUR IP never reaches any public RPC provider (this host queries upstream from its own address). BE HONEST ABOUT THE TRADE: querying a stealth address you derived LINKS that address, your session, and the time of interest AT THIS RELAY — exactly the linkage stealth addressing hides from everyone else. Nothing reaches the RPC about you, but if relay-side unlinkability matters, batch several addresses (including decoys) in one sit",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "0x address (e.g. a derived stealth payment address)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "NULL Pay — IP-blind balance read"
}{
"name": "null_calls_info",
"description": "What the blind call relay offers (1:1 and conference, codecs, join-token model). Media keys are sealed through the feed and never reach the relay. Calls themselves need a media-capable client (browser); agents can read the posture and hand a human the join flow.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "NULL Calls - capabilities of the IP-blind voice/video relay"
}{
"name": "null_capsule_cancel",
"description": "Destroys a future-dated capsule you sent with {holdMs, cancellable:true}, using its one-time cancel token. Already-released rows are untouchable. The token proves nothing about who you are. Private-lane-only: use the stdio door.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"token"
],
"properties": {
"token": {
"type": "string",
"description": "the one-time cancel token returned when the capsule was sent (20-64 url-safe chars)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
},
"title": "NULL Lifeline - cancel an UNRELEASED time capsule (\"I am safe\") (lane)"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.ox31461/robyn"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.ox31461/robyn"}) over MCP.
robyn_submit ~579 tokensrobyn_settle ~407 tokensrobyn_quote ~396 tokensrobyn_preflight ~377 tokensnull_prekeys_publish ~373 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.ox31461%2Frobyn?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ox31461%2Frobyn?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ox31461%2Frobyn.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ox31461%2Frobyn.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.ox31461%2Frobyn?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b9215d8b440c8aac…, first seen 2026-10-17, included at leaf 2035 of 30,094. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable finance servers · most reliable communication servers · most reliable security servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 02:06 UTC, the Ox31461 Robyn MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 38 outages in 90 days, with a median recovery of 2 minutes.
Ox31461 Robyn MCP server advertises 87 tools, including null_agent_guide, null_balance, null_calls_info, null_capsule_cancel, null_ecosystem.
Point your MCP client at this streamable-http endpoint: https://api.anygas.xyz/mcp
Glimind scanned all 87 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.