CandleFeed

ai.candlefeedPublished by candlefeed.aiv0.1.5Updated Oct 24, 2026

Rebuild Binance USD-M order book days for spread and depth; candles, funding, OI and liquidations

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Lets an assistant pull Binance USD-M futures market data — order book depth, candles, funding, open interest and liquidations — via CandleFeed.

What you can do
CandleFeed is a local MCP server that gives an assistant access to Binance USD-M futures market data through the CandleFeed service. According to the registry description, it can rebuild order book days for spread and depth analysis, and retrieve candles, funding rates, open interest and liquidation data. It runs as a local process over stdio and authenticates with a CandleFeed API key.
When to use it
Use it when an assistant needs Binance USD-M futures data for market analysis, such as reconstructing order book depth, examining spreads, or reviewing funding, open interest and liquidation figures. It suits research and analysis workflows rather than live trading execution.
Requirements
Runs as a local process on the user's machine (desktop only), started with uvx from the PyPI package candlefeed-mcp. Requires a CandleFeed API key supplied through the CANDLEFEED_API_KEY environment variable; a free key is available from the provider's signup page. Network access is needed to reach the CandleFeed service.
Before you install
The server requires the secret CANDLEFEED_API_KEY, which is sent to the CandleFeed service; keep it out of shared logs and configuration. Market data is retrieved from a third party, so accuracy and availability depend on that service. The description does not indicate any trading, payment or write actions.

Installation

In SourceWeft

  1. Open CandleFeed 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.

Tools

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

Version history

4
  1. v0.1.5LatestOct 15, 2026
  2. v0.1.4Oct 10, 2026
  3. v0.1.3Oct 10, 2026
  4. v0.1.2Oct 9, 2026

Score

15% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.