Oracle Feeds Mcp

io.github.rileybuildsPublished by GitHub account rileybuildsv0.1.0Updated Oct 27, 2026

On-chain price oracles: Chainlink (5 chains) + Pyth, staleness-flagged, no forced RPC key.

VerifiedSTDIODesktop onlyDatabasesFinance

Overview

AI-generated overview

Read-only MCP server that lets an assistant fetch on-chain price oracle data from Chainlink and Pyth, with timestamps and staleness flags.

What you can do
  • Look up latest Chainlink prices per chain and pair, with a staleness flag
  • Fetch a specific historical Chainlink round by round ID
  • List the curated Chainlink feeds and the supported EVM chains
  • Get latest Pyth prices by symbol or raw feed ID, and historical Pyth prices at a given Unix time
  • Search Pyth's live feed catalog for symbols
When to use it
Useful when an assistant needs current or historical crypto and stablecoin prices straight from on-chain oracles, or needs to check whether a quoted price is stale before relying on it. It suits analysis and monitoring work rather than trade execution.
Requirements
Runs as a local stdio process started with Node.js (install, build, then point the client at the built entry file). No API keys or environment variables are required: Chainlink reads use free public RPC endpoints and Pyth reads use its public Hermes REST API, so network access is needed.
Before you install
Results are oracle-reported prices passed through as-is, with no cross-provider verification or trust judgment. If output is wired into an agent that trades or rebalances, risk controls are the user's responsibility. Data comes from third-party public RPC and Hermes endpoints, and the README discloses the repository is maintained by an AI agent.

Installation

In SourceWeft

  1. Open Oracle Feeds Mcp 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

oracle-feeds-mcp

An MCP server for on-chain price oracle data, covering two independent providers — Chainlink and Pyth Network — instead of one.

Why this exists

The only prior MCP server in this space, kukapay/chainlink-feeds-mcp, is Chainlink-only, hard-requires an Infura API key, has a queryPriceByRound tool that's a placeholder (it silently calls latestRoundData() again regardless of the round you asked for), and ships with no tests. This project covers the same ground plus more, and fixes those specific gaps:

chainlink-feeds-mcporacle-feeds-mcp
ProvidersChainlink onlyChainlink and Pyth
RPCRequires your own Infura keyFree public RPCs by default, no key needed
Historical round lookupPlaceholder — re-fetches latest roundReal getRoundData(roundId) call
StalenessNot surfacedEvery result flags stale: true/false based on the feed's own on-chain/publish timestamp
Feed discoveryStatic list onlyStatic Chainlink registry plus live search over Pyth's full catalog (searchPythFeeds)
TestsNone21 tests covering staleness math, feed lookup, and both providers (network calls mocked)

This is a data-access tool: it returns oracle-reported prices as-is, with a timestamp and an age-based staleness flag. It does not attempt to verify, reconcile, or arbitrate between providers — if you need a "which source is more trustworthy" judgment, that's a different, harder problem this project deliberately does not take on.

Downstream use note: oracle price data is commonly consumed by autonomous on-chain trading or rebalancing agents. This server is read-only and moves no funds itself, but if you wire its output into an agent that executes trades, you are responsible for whatever risk controls that agent needs — this tool has no opinion on trade sizing, slippage, or execution safety.

Tools

  • getChainlinkPrice({ chain, pair }) — latest Chainlink price, with staleness flag.
  • getChainlinkRoundPrice({ chain, pair, roundId }) — a specific historical Chainlink round.
  • listChainlinkFeeds() — every chain + pair in the curated Chainlink registry.
  • listSupportedChains() — just the chain list.
  • getPythPrice({ symbol }) — latest Pyth price, by symbol (SOL/USD) or raw feed ID.
  • getPythHistoricalPrice({ symbol, unixTimestamp }) — Pyth price as of a given time.
  • searchPythFeeds({ query }) — search Pyth's live catalog (hundreds of feeds, not hardcoded).

Every price result includes updatedAt, ageSeconds, and stale (age beyond a 1-hour default threshold).

Coverage

Chainlink feeds are a curated registry (not an exhaustive mirror) across 5 EVM chains — Ethereum, Base, Arbitrum, Polygon, Optimism — with major pairs (BTC, ETH, USDC, USDT, DAI, LINK, SOL, and a few chain-native assets) on each. See src/feeds/chainlink.ts; it's a plain data file, easy to extend with more chains or pairs.

Pyth coverage is effectively everything in Pyth's live catalog — searchPythFeeds and getPythPrice query Hermes directly rather than vendoring a static list, so new Pyth feeds show up automatically.

Install & run

bash
npm installnpm run buildnpm start

Runs as a standard stdio MCP server — point any MCP client at node dist/index.js.

No API keys or environment variables are required. Chainlink reads use free public RPC endpoints (*.publicnode.com); Pyth reads use its public Hermes REST API.

Development

bash
npm test        # 21 tests, network calls mockednpm run typecheck

Disclosure

This repository is built and maintained by an AI agent (rileybuilds), operating with human oversight. See the account bio.

License

MIT

Source: README.md at commit 002a858

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

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