MCP.so
Sign In
P

Pyth Pro Mcp

@pyth-network

About Pyth Pro Mcp

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "pyth-mcp": {
      "type": "streamable-http",
      "url": "https://mcp.pyth.network/mcp"
    }
  }
}

Tools

5

List available Pyth Pro price feeds. Use this FIRST to discover what feeds exist before calling get_latest_price, get_historical_price, or get_candlestick_data. Filter by asset_type (crypto, equity, fx, metal, rates, commodity, funding-rate) or search by name/symbol. Returns feed metadata including pyth_lazer_id (needed for get_historical_price), symbol, asset_type, and exponent.

Convert a date string to Unix timestamp for use with get_historical_price and get_candlestick_data. Use this tool when you need to compute timestamps β€” do not calculate Unix timestamps manually. Accepts ISO 8601 dates (e.g. '2026-01-01', '2026-01-01T12:00:00Z'). Returns seconds, microseconds, ISO 8601, and whether the date is within the available data range (April 2025 onward).

Fetch OHLC candlestick data for a symbol. Pass your Pyth Pro `access_token` to authenticate the request. Use for charting, technical analysis, backtesting. IMPORTANT: The symbol must be the full name from get_symbols including the asset type prefix (e.g. 'Crypto.BTC/USD', 'Equity.US.AAPL', 'FX.EUR/USD') β€” never use bare names like 'BTC/USD'. Historical data is available from April 2025 onward β€” do not request timestamps before that. Resolutions: 1/5/15/30/60 minutes, 120/240/360/720 (multi-hour), D (daily), W (weekly), M (monthly). Timestamps are Unix seconds. Timestamp reference (Unix seconds): 2025-04-01 (earliest available) = 1743465600 2026-01-01 = 1767225600 2026-06-01 = 1780272000 Always double-check your timestamp math β€” year-boundary errors are common.

Get price data for specific feeds at a historical timestamp. Pass your Pyth Pro `access_token` to authenticate the request. Use get_symbols first to find feed IDs or symbols. If both price_feed_ids and symbols are provided, only price_feed_ids are used. Accepts Unix seconds, milliseconds, or microseconds (auto-detected). Historical data is available from April 2025 onward β€” do not request timestamps before that. The timestamp is internally converted to microseconds and aligned (rounded down) to the channel rate β€” e.g. for fixed_rate@200ms, it must be divisible by 200,000ΞΌs. Prices are integers with an exponent field β€” human-readable price = price * 10^exponent. Pre-computed display_price fields are included for convenience. Timestamp reference: 2025-04-01 (earliest available) = 1743465600 2026-01-01 = 1767225600 2026-06-01 = 1780272000 Always double-check your timestamp math β€” year-boundary errors are common.

Get the most recent real-time price for one or more feeds. Requires an `access_token` parameter (get one at https://docs.pyth.network/price-feeds/pro/acquire-access-token). Use get_symbols first to find symbols or feed IDs. IMPORTANT: symbols must be the full name including asset type prefix (e.g. 'Crypto.BTC/USD', not 'BTC/USD'). If both price_feed_ids and symbols are provided, only price_feed_ids are used. Prices are integers with an exponent field β€” human-readable price = price * 10^exponent. Pre-computed display_price fields are included for convenience.

Overview

What is Pyth Pro Mcp?

β€”

How to use Pyth Pro Mcp?

β€”

Key features of Pyth Pro Mcp?

β€”

Use cases of Pyth Pro Mcp?

β€”

FAQ from Pyth Pro Mcp

What does Pyth Pro Mcp do?

β€”

How does it compare to alternatives?

β€”

What are the dependencies or runtime requirements?

β€”

Where does the data live?

β€”

What transports or authentication does it support?

β€”

Comments

More Other MCP servers