Binance Market Data MCP Server

Created By
qeinfinitya year ago
Overview

what is Binance Market Data MCP Server?

Binance Market Data MCP Server is an implementation designed to access Binance market data using a WebSocket connection, providing real-time financial data.

how to use Binance Market Data MCP Server?

To use the MCP Server, clone the repository, install the required dependencies using npm, and build the project to start accessing market data through WebSocket and REST API.

key features of Binance Market Data MCP Server?

  • Real-time market data access via WebSocket
  • REST API for both spot and futures markets
  • Support for a variety of data types including prices, volumes, and order books
  • Futures-specific data like funding rates and open interest
  • Automatic WebSocket reconnection for uninterrupted data streams
  • Implements rate limiting and error handling for smooth operation

use cases of Binance Market Data MCP Server?

  1. Tracking real-time cryptocurrency prices and trading volumes.
  2. Analyzing order book data for strategic trading decisions.
  3. Monitoring futures market data including funding rates and open interest.

FAQ from Binance Market Data MCP Server?

  • What type of data can I access through this server?

You can access market prices, volume, order book data, trade information, and futures-specific data such as funding rates and open interest.

  • How can I install it?

Clone the repository, run npm install to install dependencies, and run npm run build to set up the server.

  • Is WebSocket support available?

Yes, the server provides real-time market data via a WebSocket connection.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
qeinfinity
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago