Home / MCP registry index / ai.apexrunner/signals

APEX Runner Crypto Signals

ai.apexrunner/signals in the official MCP registry. Endpoint https://apexrunner.ai/mcp.

The registry describes it as: Live crypto market signals for trading agents, pay-per-call in USDC on Base 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 signals https://apexrunner.ai/mcp

{
  "mcpServers": {
    "signals": {
      "url": "https://apexrunner.ai/mcp"
    }
  }
}

code --add-mcp '{"name":"signals","type":"http","url":"https://apexrunner.ai/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 lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_free_market_snapshot apex_alpha_score grid_health_score regime_confluence liquidation_pressure combined_alpha apex_composite arb_spread regime_transition whale_sentiment grid_health trend_confirmed altcoin_season mean_reversion_scan token_unlock liquidation_magnet portfolio_heat grid_levels funding_rate dca_signal btc_dominance funding_rate_hl regime bb_analysis volume_analysis fear_greed apex_pulse market_tick regime_transition_probability apex_evolution_insight market_pulse_bundle trading_intelligence_bundle risk_assessment_bundle signal_intelligence my_pricing apex_trial slippage_forecast optimal_order_routing execution_window_optimizer crowded_trade_detector agent_conviction_score narrative_intelligence capital_rotation_signal agent_stress_index btc_price_tick fg_micro regime_micro funding_tick vol_tick

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): 4b42142fe4b07024. 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/ai-apexrunner-signals/badge.svg)](https://lazaretto.dev/mcp-registry/ai-apexrunner-signals)

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

Crypto and Web3 MCP servers · Finance and markets MCP servers