MCP server: One MCP server.

AgentCanary

@mrcerqRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

Retired compatibility stub for AgentCanary MCP. Daily briefs continue on X and Telegram.

Crypto marketsv1.4.8JavaScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmagentcanary-mcpv1.4.8

Run

npx -y agentcanary-mcp

MCP client config

{
  "mcpServers": {
    "agentcanary": {
      "command": "npx",
      "args": [
        "-y",
        "agentcanary-mcp"
      ]
    }
  }
}
README1 min read

AgentCanary MCP Server

AgentCanary's public API and MCP product were retired on 2026-07-09.

The npm package remains as a compatibility stub so existing MCP clients start cleanly and receive a clear retirement notice instead of failing on API keys or retired endpoints.

Daily AgentCanary briefs continue here:

Usage

bash
npx agentcanary-mcp

No configuration is required. All legacy tools return the same retired-status payload with the current X and Telegram locations.

Tools

The server keeps the legacy tool names registered for compatibility:

  • get_briefs
  • get_indicators
  • get_regime
  • get_predictions
  • get_narratives
  • get_news
  • get_scores
  • get_scenario_analysis
  • get_signals
  • get_defi
  • get_btc_options
  • get_market_structure
  • get_central_banks
  • get_expectations
  • get_macro
  • get_open_interest
  • get_liquidations
  • diagnose
  • get_track_record

These tools do not contact retired AgentCanary product endpoints.

Similar modules

Browse Crypto markets