io.github.pythia-the-oracle/pythia-oracle-mcp
PYPI · PYTHIA-ORACLE-MCP · SCANNED SEP 21
Every smart contract deserves intelligence, not just data. On-chain indicators via Chainlink.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2265 tokens (~125/item across 18 items; 18 tools + 0 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.pythia-the-oracle/pythia-oracle-mcp server?
io.github.pythia-the-oracle/pythia-oracle-mcp runs locally as a PyPI package, launched with uvx pythia-oracle-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pythia-oracle-mcp
claude mcp add pythia-the-oracle-pythia-oracle-mcp -- uvx pythia-oracle-mcp
{
"mcpServers": {
"pythia-the-oracle-pythia-oracle-mcp": {
"command": "uvx",
"args": [
"pythia-oracle-mcp"
]
}
}
} {
"servers": {
"pythia-the-oracle-pythia-oracle-mcp": {
"command": "uvx",
"args": [
"pythia-oracle-mcp"
]
}
}
} codex mcp add pythia-the-oracle-pythia-oracle-mcp -- uvx pythia-oracle-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pythia-the-oracle-pythia-oracle-mcp": {
"type": "local",
"command": [
"uvx",
"pythia-oracle-mcp"
],
"enabled": true
}
}
} openclaw mcp add pythia-the-oracle-pythia-oracle-mcp --command uvx --arg pythia-oracle-mcp
mcp_servers:
pythia-the-oracle-pythia-oracle-mcp:
command: "uvx"
args: ["pythia-oracle-mcp"] {
"McpServers": {
"pythia-the-oracle-pythia-oracle-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"pythia-oracle-mcp"
]
}
}
} assistant mcp add pythia-the-oracle-pythia-oracle-mcp -t stdio -c uvx -a pythia-oracle-mcp
{
"mcpServers": {
"pythia-the-oracle-pythia-oracle-mcp": {
"command": "uvx",
"args": [
"pythia-oracle-mcp"
]
}
}
} 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.
- 21 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
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 · Analysed pypi/pythia-oracle-mcp@0.12.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_oracle_health ~74
Check the reliability and uptime of Pythia's oracle system. Returns per-token 30-day uptime (sorted worst-first so problems surface immediately), recent daily status history, data source health, and infrastructure status. Use this to verify Pythia's reliability before integrating or relying on its data.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_contracts ~25
Get Pythia contract addresses for on-chain integration. Shows all supported chains.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_events_guide ~54
Get Solidity code to subscribe to Pythia Events (indicator alerts). Returns a complete contract that approves LINK, subscribes to an indicator alert, listens for PythiaEvent, and can cancel for a refund.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_events_info ~59
Get overview of Pythia Events — on-chain indicator alert subscriptions. Returns pricing, supported conditions, subscriber flow, registry addresses per chain, and current subscription stats. Events let you subscribe once and get notified when an indicator crosses a threshold.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_feed_value ~195
Get the latest computed value of a Pythia indicator feed. Reads from the live cache (feed_values table) populated by the indicator pipeline on every cycle. Off-chain AI agents use this when reasoning about a Vision context, choosing an Event threshold, or sanity-checking a feed's current level. On-chain consumers should request the value through oracle.request() to get a Chainlink-attested response — see get_integration_guide(). Args: feed_name: full feed name (e.g. 'bitcoin_RSI_1H_14', 'pol_EMA_5M_20'). Returns: Latest value + computed_at + chain, one block per chain if a feed exists on multiple chains. If the feed has no cached value, returns a diagnostic pointer (warm-up window, deactivated, or unknown name).
| Name | Type | Req | Description |
|---|---|---|---|
| feed_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_indicator_history ~446
Read Pythia's public, immutable indicator history for a feed over a date range — and optionally settle a condition against it. Backed by the free day-file archive at https://pythia.c3x-solutions.com/history/{chain}/{feed_name}/{YYYY-MM-DD}.json (one file per feed per closed UTC day, 5-minute points, never rewritten once published). Use it to audit or re-derive "was RSI below 30 at any point last week?", to reconstruct what a Vision or Event saw, to backtest a threshold before subscribing to an Event, or to settle a prediction-market style question from public inputs anyone can re-fetch and verify. Args: feed_name: full feed name, same key as Feeds/Events (e.g. 'bitcoin_RSI_1D_14'). start_date: first UTC day, YYYY-MM-DD (inclusive). end_date: last UTC day, YYYY-MM-DD (inclusive). Defaults to start_date. At most 31 days per call — split longer ranges. chain: delivery chain the feed is archived for (e.g. 'polygon'). Only needed when the manifest lists the feed on more than one chain. condition: optional 'ABOVE' or 'BELOW' — with threshold, evaluates whether ANY point in the range satisfies it. threshold: numeric threshold for condition, in the feed's own units. Returns: Per-day coverage (points, min, max, first, last), the range summary, the day-file URLs used (so a verifier can re-fetch the exact inputs), and — when condition+threshold are given — a verdict: TRUE (first matching timestamp + value), FALSE (full coverage, no match), or INSUFFICIENT_DATA (missing day-files or gaps large enough that FALSE cannot be asserted). Never interpolates across gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| condition | string | – | – |
| end_date | string | – | – |
| feed_name | string | yes | – |
| start_date | string | yes | – |
| threshold | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_integration_guide ~124
Get Solidity code to integrate Pythia into a smart contract. Args: tier: 'discovery' (single value), 'analysis', 'speed', or 'complete'. chain: Optional chain key (e.g. 'mainnet', 'amoy', 'arbitrum'). When unset, the embedded Solidity uses the first available chain's addresses (Polygon mainnet by convention) and the prose lists every chain where this tier's consumer is deployed.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| tier | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_market_summary ~63
Get a summary of all tokens tracked by Pythia with operational overview. Returns system-wide stats, tokens grouped by status, uptime distribution, data source health, and infrastructure status. Useful for quickly understanding what Pythia covers and whether the system is healthy.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_pricing ~28
Get Pythia pricing tiers and free trial info. Prices are live from the data feed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_token_feeds ~117
Get all available indicator feeds for a specific token. Shows every feed name (EMA, RSI, Bollinger, Volatility across all timeframes), the token's reliability stats, and data source count. Feed names are what you pass to the on-chain oracle to request data. Args: engine_id: Token engine ID (e.g., 'bitcoin', 'solana', 'bittensor', 'aave', 'pol'). Use list_tokens() to see all available IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| engine_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_vision_history ~67
Get recent Pythia Visions fired for a token with pattern breakdown and stats. Args: token: Token symbol to check (default: BTC). Case-insensitive. For the live list of Vision tokens call get_visions_info().
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_vision_payload ~215
Get the full enriched object for a fired Pythia Vision by id. Returns the rich AI-facing companion to the on-chain VisionFired event: pattern metadata with numeric ranges, failure profile (avg return when correct, avg drawdown when wrong, worst drawdown), cooldown context (hours since last same-pattern fire on this token, confidence delta vs last fire), and concurrent fires from other tokens within the last 24h. Lightweight on-chain consumers can decode the VisionFired payload bytes directly. AI agents reasoning about a specific Vision should use this tool — it contains the data needed to size positions and compare against historical failure modes, which the on-chain event payload does not. Args: vision_id: integer id of the Vision (returned by get_vision_history) Returns: Multi-section text report. If vision_id is not in the recent window (last 20 fires per token), returns a helpful pointer to history.
| Name | Type | Req | Description |
|---|---|---|---|
| vision_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_visions_guide ~74
Get Solidity code to subscribe to Pythia Visions and listen for VisionFired events. Returns a complete contract that subscribes to the PythiaVisionRegistry, receives VisionFired events with pattern type, confidence, direction, price, and full analysis payload. Subscription is FREE (no LINK required).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_visions_info ~96
Get overview of Pythia Visions — walk-forward validated market intelligence on-chain. Returns the walk-forward validated patterns with accuracy stats, the Vision Registry contract address, subscription info (FREE), evaluation frequency, and supported tokens. Visions are pattern detections that passed walk-forward validation across multiple years of history. Live token + pattern set is returned in the response (canonical source: feed-status.json visions section).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_subscriptions ~125
Enumerate active Pythia Event subscriptions owned by an address. Returns every subscription where active=true (not yet fired, expired, or cancelled). Without this tool, dApps and dashboards have to replay every SubscriptionCreated log from the registry deploy block to discover what an owner is currently subscribed to. Args: owner_address: subscriber wallet address ('0x...', case-insensitive). Returns: Multi-section report listing each active subscription with feed name, condition + threshold, expiry, registry address, and creation tx.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_tokens ~66
List all tokens tracked by Pythia with status and reliability info. Returns token symbols, categories, data source count, 30-day uptime, and operational status. Covers cross-chain tokens (BTC, SOL, TAO, RENDER, ONDO, etc.) and DeFi tokens.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lookup_event_feed ~166
Reverse-lookup a Pythia Event feedId (bytes32) to its human-readable feed name. Subscribers receive `bytes32 feedId` in SubscriptionCreated and PythiaEvent events. This tool maps that hash back to the canonical feed name (e.g. 'pol_RSI_5M_14') so dApps don't need to maintain their own feedId → name table or query the registry contract on every event. Args: feed_id_hex: bytes32 hash, with or without '0x' prefix, any case. Returns: Single-section report with feed_name + matching token + indicator suffix. If the hash is not in the registered lookup table, returns a diagnostic pointer.
| Name | Type | Req | Description |
|---|---|---|---|
| feed_id_hex | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
subscribe_info ~121
Plan a specific Pythia Events subscription with cost and exact calls. Args: feed_name: Feed name to monitor (e.g. 'pol_RSI_5M_14', 'bitcoin_EMA_1H_20') condition: 0=ABOVE, 1=BELOW, 2=CROSSES_ABOVE, 3=CROSSES_BELOW days: Subscription duration in days (1-365)
| Name | Type | Req | Description |
|---|---|---|---|
| condition | integer | – | – |
| days | integer | – | – |
| feed_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.pythia-the-oracle/pythia-oracle-mcp server?
io.github.pythia-the-oracle/pythia-oracle-mcp is listed in the public MCP registry as io.github.pythia-the-oracle/pythia-oracle-mcp. Every smart contract deserves intelligence, not just data. On-chain indicators via Chainlink. This page covers its PyPI package (pythia-oracle-mcp).
Is the io.github.pythia-the-oracle/pythia-oracle-mcp server safe to use?
io.github.pythia-the-oracle/pythia-oracle-mcp scores 58 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 io.github.pythia-the-oracle/pythia-oracle-mcp server expose?
io.github.pythia-the-oracle/pythia-oracle-mcp exposes 18 tools: list_tokens, get_token_feeds, get_market_summary, check_oracle_health, get_contracts, and 13 more. Their descriptions and schemas cost roughly 2,115 tokens of context every time the server is loaded.
Is the io.github.pythia-the-oracle/pythia-oracle-mcp server still maintained?
io.github.pythia-the-oracle/pythia-oracle-mcp 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.