Home / MCP registry index / io.fexr/trading

Fexr trading

io.fexr/trading in the official MCP registry. Endpoint https://api.fexr.io/v1/mcp/trade.

The registry describes it as: Let your AI trade inside limits you set: proven strategies, hard limits, every move on record.

Connect it

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

claude mcp add --transport http trading https://api.fexr.io/v1/mcp/trade

{
  "mcpServers": {
    "trading": {
      "url": "https://api.fexr.io/v1/mcp/trade"
    }
  }
}

code --add-mcp '{"name":"trading","type":"http","url":"https://api.fexr.io/v1/mcp/trade"}'

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 lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_asset_metrics get_historical_timeseries get_derivatives get_exchange_market_data get_stablecoins get_protocol_financials get_network_activity get_staking_yields get_token_unlocks get_fundraising get_treasury get_catalysts get_market_signals get_predictive_signals get_smart_money_flow get_whale_alerts get_market_pulse get_sentiment_mindshare get_proposal_tracking run_screener get_news_trending get_whale_board review_address get_trader get_asset_snapshot list_proven_strategies read_ask_thread get_trade_plan get_weekly_review run_token_dossier get_my_account ask_ai_copilot get_my_mandate start_strategy stop_strategy close_position set_stop place_order pause_trading

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-11-12): ad21e60e6da4ce97. 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.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

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

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. How tool poisoning works. What we found across the registry. Check another server.

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

Finance and markets MCP servers