MCP servers observed by Lowdown
io.github.ox31461/robyn MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 87 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ox31461/robyn
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ox31461/robyn?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
87 tools on 2026-11-16:
null_agent_guidenull_balancenull_calls_infonull_capsule_cancelnull_ecosystemnull_login_verifynull_market_delistnull_market_listnull_market_listingsnull_names_marketnull_names_quotenull_notarizenull_prekeys_fetchnull_prekeys_publishnull_prov_issuernull_prov_mintnull_transparencynull_void_descriptornull_void_directorynull_void_publishnull_witness_headnull_witness_rangerobyn_7702_checkrobyn_7702_delegaterobyn_attestationrobyn_capability_snapshotrobyn_changelogrobyn_counterparty_checkrobyn_cross_chainrobyn_delivery_statsrobyn_errorsrobyn_evidence_bundlerobyn_fee_forensicsrobyn_improve_costrobyn_integration_lintrobyn_mandate_certificaterobyn_mandate_checkrobyn_mandate_cosign_requestrobyn_mandate_eventsrobyn_mandate_listrobyn_mandate_statusrobyn_meshrobyn_message_anchor_proofrobyn_message_directoryrobyn_message_erasurerobyn_message_feedrobyn_message_inforobyn_message_mailbox_ofrobyn_message_publish_mailboxrobyn_message_sendrobyn_netting_accountrobyn_netting_enroll_payloadrobyn_netting_inforobyn_netting_previewrobyn_netting_reservesrobyn_netting_statementrobyn_netting_transfer_payloadrobyn_payment_request_preparerobyn_payment_request_settlementrobyn_payment_request_verifyrobyn_planrobyn_plus_claimrobyn_plus_inforobyn_plus_invoicerobyn_plus_invoice_statusrobyn_plus_trialrobyn_preflightrobyn_preflight_fullrobyn_preparerobyn_privacy_posturerobyn_quoterobyn_receipt_deliverrobyn_receipt_verifyrobyn_recipesrobyn_refusal_verifyrobyn_route_statusrobyn_sandbox_dorobyn_settlerobyn_spend_statementrobyn_sponsor_7702robyn_submitrobyn_verify_outcomerobyn_vip_statusrobyn_why_this_routerobyn_yield_accountrobyn_yield_quoterobyn_yield_spend
MCP Registry declaration
- Registry name:
io.github.ox31461/robyn - Declared version: 1.0.5
- Status: active
- Declared hosts:
api.anygas.xyz
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.ox31461/robyn", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ox31461/robyn?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.ox31461/robyn -- npx -y anygas-mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).