AgentCanary

io.github.MrCerqPublished by GitHub account MrCerqv1.4.8Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A retired compatibility stub for the AgentCanary MCP server; it starts cleanly but every legacy tool only returns a retirement notice.

What you can do
Legacy tool names remain registered for compatibility, covering briefs, indicators, regime, predictions, narratives, news, scores, scenario analysis, signals, DeFi, BTC options, market structure, central banks, expectations, macro, open interest, liquidations, diagnostics and track record. All of them return the same retired-status payload pointing to the current X and Telegram locations. The tools do not contact the retired AgentCanary product endpoints. No live market data, analysis or diagnostics are produced.
When to use it
Only if an existing MCP client configuration still references agentcanary-mcp and you want it to start without failing on API keys or retired endpoints. It is not useful for obtaining market briefs or analysis, which have moved to X and Telegram.
Requirements
Runs locally over stdio, typically via npx with the npm package agentcanary-mcp. No configuration, API keys, environment variables or headers are required.
Before you install
The underlying product was retired on 2026-07-09, so no real data or analysis is available. Do not expect the legacy tools to return market information; they only report the retirement and point to external channels.

Installation

In SourceWeft

  1. Open AgentCanary in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

Source: README.md at commit 1432be8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.4.8LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.