Home / MCP registry index / com.imagiolabs.www/imagio-relay

Imagio Relay

com.imagiolabs.www/imagio-relay in the official MCP registry. Endpoint https://relay.imagiolabs.com/mcp. Source: github.com/andyrzr-bot/imagio-relay.

The registry describes it as: 57 deterministic web-intel, trade and infra tools for agents. USDC per call via x402.

Connect it

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

claude mcp add --transport http imagio-relay https://relay.imagiolabs.com/mcp

{
  "mcpServers": {
    "imagio-relay": {
      "url": "https://relay.imagiolabs.com/mcp"
    }
  }
}

code --add-mcp '{"name":"imagio-relay","type":"http","url":"https://relay.imagiolabs.com/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.

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

Tools it advertises

health market watch links wallet summarize sanitize manifest_validate decode_tx html_to_md diff nl_sql risk_grade audit_claims gas_forecast api_health whale catalyst prices kpi state_token repo_sup pr_review localize seal open receipt_verify rss_gate data_pack earnings_calendar insider_trades short_interest macro_calendar options_iv analyst_ratings 13f_holdings dividend_calendar funding_rates liquidations token_unlocks defi_tvl dex_volume onchain_whale_flow stablecoin_flows crypto_sentiment gas_oracle mev_scan

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 9d30135763e6d584. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-imagiolabs-www-imagio-relay/badge.svg)](https://lazaretto.dev/mcp-registry/com-imagiolabs-www-imagio-relay)

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.

Related

Crypto and Web3 MCP servers