Pyth Pro MCP Server
REMOTE · MCP.PYTH.NETWORK · SCANNED SEP 21
Real-time and historical price feeds for 500+ crypto, equities, FX, and commodities assets.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1507 tokens (~115/item across 13 items; 5 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Pyth Pro MCP Server server?
Pyth Pro MCP Server is a hosted endpoint at https://mcp.pyth.network/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.pyth.network
claude mcp add --transport http pyth-network-mcp 'https://mcp.pyth.network/mcp'
{
"mcpServers": {
"pyth-network-mcp": {
"url": "https://mcp.pyth.network/mcp"
}
}
} {
"servers": {
"pyth-network-mcp": {
"type": "http",
"url": "https://mcp.pyth.network/mcp"
}
}
} [mcp_servers.pyth-network-mcp] url = "https://mcp.pyth.network/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pyth-network-mcp": {
"type": "remote",
"url": "https://mcp.pyth.network/mcp",
"enabled": true
}
}
} openclaw mcp add pyth-network-mcp --url 'https://mcp.pyth.network/mcp' --transport streamable-http
mcp_servers:
pyth-network-mcp:
url: "https://mcp.pyth.network/mcp" {
"McpServers": {
"pyth-network-mcp": {
"Transport": "http",
"Url": "https://mcp.pyth.network/mcp"
}
}
} assistant mcp add pyth-network-mcp -t streamable-http -u 'https://mcp.pyth.network/mcp'
{
"mcpServers": {
"pyth-network-mcp": {
"type": "http",
"url": "https://mcp.pyth.network/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 0
- HSTS header: pass → fail ▼ security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp.pyth.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pyth.network | CN=YE1,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6b48bebc2a3f646cd6c98ace20ec0322ba3 |
| SANs: *.blue.pyth.network, *.devnet.pyth.network, *.indigo.pyth.network, *.mainnet.pyth.network, *.pyth.network, *.pythnet.pyth.network, *.pythtest.pyth.network, *.testnet.pyth.network, *.violet.pyth.network, pyth.network | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.pyth.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 40414 | 8 | Verified |
| pyth.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pyth.network/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.pyth.network/mcp | HTTPS enforced | 301 | https://mcp.pyth.network/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
convert_date_to_timestamp Convert Date to Timestamp ~170
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).
| Name | Type | Req | Description |
|---|---|---|---|
| date_string | string | yes | Date to convert. Must be ISO 8601 / RFC 3339 with timezone (e.g. '2026-01-01T00:00:00Z', '2026-01-01'). Bare dates without timezone are interpreted as UTC. |
No output schema declared.
No examples provided.
get_candlestick_data Get Candlestick Data ~407
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Pyth Pro access token used to authenticate the request. Get one at https://docs.pyth.network/price-feeds/pro/acquire-access-token |
| channel | string | – | Override default channel (e.g. fixed_rate@200ms, real_time, fixed_rate@50ms, fixed_rate@1000ms) |
| from | integer | yes | Start time (Unix seconds) |
| resolution | string | yes | Candle size: 1, 5, 15, 30, 60 (minutes), 120, 240, 360, 720 (hours), D (daily), W (weekly), M (monthly) |
| symbol | string | yes | Full symbol from get_symbols including asset type prefix (e.g. 'Crypto.BTC/USD', not 'BTC/USD') |
| to | integer | yes | End time (Unix seconds) |
No output schema declared.
No examples provided.
get_historical_price Get Historical Price ~380
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Pyth Pro access token used to authenticate the request. Get one at https://docs.pyth.network/price-feeds/pro/acquire-access-token |
| channel | string | – | Override default channel (e.g. fixed_rate@200ms, real_time, fixed_rate@50ms, fixed_rate@1000ms) |
| price_feed_ids | array | – | Numeric feed IDs from get_symbols |
| symbols | array | – | Full symbol names from get_symbols including asset type prefix (e.g. ['Crypto.BTC/USD', 'Equity.US.AAPL/USD']) |
| timestamp | number | yes | Unix timestamp — accepts seconds, milliseconds, or microseconds (auto-detected by magnitude) |
No output schema declared.
No examples provided.
get_latest_price Get Latest Price ~272
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | Pyth Pro access token. Get one at https://pyth.network/pricing |
| channel | string | – | Override default channel (e.g. fixed_rate@200ms, real_time, fixed_rate@50ms, fixed_rate@1000ms) |
| price_feed_ids | array | – | Numeric feed IDs from get_symbols |
| properties | array | – | Properties to return. Default: price, bestBidPrice, bestAskPrice, confidence, exponent, publisherCount |
| symbols | array | – | Full symbol names from get_symbols including asset type prefix (e.g. ['Crypto.BTC/USD', 'Equity.US.AAPL/USD']) |
No output schema declared.
No examples provided.
get_symbols List Pyth Price Feeds ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Filter by asset type: crypto, fx, equity, metal, rates, commodity, funding-rate |
| limit | integer | – | Results per page (default 50, max 200) |
| offset | integer | – | Pagination offset (default 0) |
| query | string | – | Text filter (e.g. 'BTC', 'gold', 'AAPL') |
No output schema declared.
No examples provided.
What is the Pyth Pro MCP Server server?
Pyth Pro MCP Server is listed in the public MCP registry as io.github.pyth-network/mcp. Real-time and historical price feeds for 500+ crypto, equities, FX, and commodities assets. This page covers its hosted endpoint (https://mcp.pyth.network/mcp).
Is the Pyth Pro MCP Server server safe to use?
Pyth Pro MCP Server scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pyth Pro MCP Server server expose?
Pyth Pro MCP Server exposes 5 tools: get_symbols, convert_date_to_timestamp, get_candlestick_data, get_historical_price, get_latest_price. Their descriptions and schemas cost roughly 1,403 tokens of context every time the server is loaded.
Does the Pyth Pro MCP Server server require authentication?
No. We connected to Pyth Pro MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pyth Pro MCP Server server still maintained?
Pyth Pro MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.