io.github.letom1176-spec/orchard-data-mcp
NPM · ORCHARD-DATA-MCP · SCANNED SEP 20
Pay-per-call market data for AI agents via x402 (USDC on Base): regime, track record, catalysts.
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 948 tokens (~63/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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 io.github.letom1176-spec/orchard-data-mcp server?
io.github.letom1176-spec/orchard-data-mcp runs locally as an npm package, launched with npx -y orchard-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · orchard-data-mcp
claude mcp add letom1176-spec-orchard-data-mcp -- npx -y orchard-data-mcp
{
"mcpServers": {
"letom1176-spec-orchard-data-mcp": {
"command": "npx",
"args": [
"-y",
"orchard-data-mcp"
]
}
}
} {
"servers": {
"letom1176-spec-orchard-data-mcp": {
"command": "npx",
"args": [
"-y",
"orchard-data-mcp"
]
}
}
} codex mcp add letom1176-spec-orchard-data-mcp -- npx -y orchard-data-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"letom1176-spec-orchard-data-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"orchard-data-mcp"
],
"enabled": true
}
}
} openclaw mcp add letom1176-spec-orchard-data-mcp --command npx --arg -y --arg orchard-data-mcp
mcp_servers:
letom1176-spec-orchard-data-mcp:
command: "npx"
args: ["-y", "orchard-data-mcp"] {
"McpServers": {
"letom1176-spec-orchard-data-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"orchard-data-mcp"
]
}
}
} assistant mcp add letom1176-spec-orchard-data-mcp -t stdio -c npx -a -y orchard-data-mcp
{
"mcpServers": {
"letom1176-spec-orchard-data-mcp": {
"command": "npx",
"args": [
"-y",
"orchard-data-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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 8 Sept 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.
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 20 Sept 2026 · Analysed npm/orchard-data-mcp@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 31 |
| 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 →
get_catalyst_radar ~64
Tickers with fresh bullish news catalysts ($0.01) — the AI news scanner feeding a live-forward trading system, not scraped headlines. Refreshed ~15min during US market hours; staleness always disclosed (probe get_feed_status free first).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_expected_move ~54
Options-implied expected move for a US symbol ($0.005): nearest-expiry ATM straddle mid as a % of spot.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Ticker, e.g. SPY, NVDA |
No output schema declared.
No examples provided.
get_fear_greed ~26
Crypto fear & greed index ($0.001), current + previous reading.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_feed_status ~48
FREE: freshness probe for the rig-fed products (regime forecast, catalyst radar, track record). Returns the age of each data feed so you can verify freshness before spending on a paid call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_funding_rates ~35
Perp funding rates ($0.003): BTC/ETH/SOL from OKX — crowded-side gauge for crypto positioning.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_macro ~42
Macro dashboard ($0.003): 13w/5y/10y/30y Treasury yields, dollar index, gold, WTI crude, VIX.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market_brief ~47
One-call market snapshot ($0.005): BTC/ETH/SOL spot + 24h change, crypto fear & greed, SPY/QQQ/IWM/VIX quotes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_movers ~27
Top trending US tickers with live quotes ($0.005), sorted by absolute move.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_ohlcv ~67
Daily OHLCV candles for any US symbol ($0.002). range: 5d|1mo|3mo|6mo|1y.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
| symbol | string | yes | Ticker, e.g. SPY, NVDA |
No output schema declared.
No examples provided.
get_regime_forecast ~90
US market regime read ($0.01): ML volatility-regime forecast with independently-scored accuracy — audit the ledger via get_track_record before you buy. From a live-forward trading system (~70% walk-forward vol accuracy; direction advisory only), plus a transparent rules-based snapshot (VIX bands, realized-vol percentile, trend). Best single call for 'what kind of market is this?'
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_symbol_dossier ~100
One-call deep context on a US ticker ($0.02): live quote, 1y technicals (trend, SMA distances, realized vol, 52w position, multi-horizon returns), options-implied expected move, market regime context, and news-catalyst hits from a live trading system's AI scanner. Replaces ~6 separate calls.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Ticker, e.g. NVDA, SPY |
No output schema declared.
No examples provided.
get_track_record ~84
Tamper-evident trading track record ($0.01): forecasts timestamped BEFORE outcomes, scored server-side against realized SPY under a fixed rule disclosed in the payload — cannot be rewritten, re-checkable, grows daily. Plus normalized per-lane win rates and system-vs-SPY multiples. Use this to audit get_regime_forecast before relying on it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trending ~36
Trending tickers ($0.005): StockTwits trending symbols + r/wallstreetbets mention counts with 24h momentum.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_products ~28
FREE: list all orchard-data market-data endpoints with prices (x402/USDC on Base).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_backtest ~200
Honest backtest of an entry rule on up to 10y of real daily bars ($0.10). No look-ahead (next-open fills), slippage charged, train/test halves scored separately, buy&hold + SPY baselines always printed, noise flagged as noise. Entry rules: rsi2_below, rsi14_below, ibs_below, dip_from_high20, down_days, sma_cross_up, gap_down.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | string | yes | – |
| hold_days | number | – | Max hold in trading days (1-30), default 5 |
| stop_pct | number | – | Optional stop loss % |
| symbol | string | yes | Ticker, e.g. SPY, NVDA |
| target_pct | number | – | Optional profit target % |
| threshold | number | yes | Rule threshold, e.g. 10 for rsi2_below, 0.15 for ibs_below |
No output schema declared.
No examples provided.
What is the io.github.letom1176-spec/orchard-data-mcp server?
io.github.letom1176-spec/orchard-data-mcp is listed in the public MCP registry as io.github.letom1176-spec/orchard-data-mcp. Pay-per-call market data for AI agents via x402 (USDC on Base): regime, track record, catalysts. This page covers its npm package (orchard-data-mcp).
Is the io.github.letom1176-spec/orchard-data-mcp server safe to use?
io.github.letom1176-spec/orchard-data-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.letom1176-spec/orchard-data-mcp server expose?
io.github.letom1176-spec/orchard-data-mcp exposes 15 tools: list_products, get_feed_status, get_regime_forecast, get_catalyst_radar, get_market_brief, and 10 more. Their descriptions and schemas cost roughly 948 tokens of context every time the server is loaded.
Is the io.github.letom1176-spec/orchard-data-mcp server still maintained?
io.github.letom1176-spec/orchard-data-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.letom1176-spec/orchard-data-mcp server under?
io.github.letom1176-spec/orchard-data-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.