Skip to main content
Glama
letom1176-spec

orchard-data-mcp

by letom1176-spec
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

orchard-data-mcp

MCP server for orchard-data — pay-per-call market data for AI agents over x402 (USDC micro-payments on Base). No account, no API key, no subscription.

Try it before you spend anything. Three tools cost nothing and need no wallet: list_products, get_fear_greed, and get_feed_status.

The flagship tools are data you cannot get elsewhere: an ML market-regime forecast, a news catalyst radar, and a track record you can audit — predictions are recorded before the outcome and scored server-side against what actually happened, with the scoring rule shipped inside the payload. Produced by a real algorithmic trading system, refreshed ~15 min during US market hours, staleness always reported and never hidden.

Tools

Tool

Price/call

What

list_products

free

Product manifest with live prices

get_fear_greed

free

Crypto fear & greed index, current + previous reading

get_feed_status

free

Freshness probe — check the rig-fed products are current before paying

run_backtest ⭐

$0.10

Backtest your own entry rule on up to 10y of real daily bars: next-open fills (no look-ahead), slippage charged, train/test halves scored apart, buy&hold + SPY baselines always printed, disagreeing halves reported as noise

get_symbol_dossier

$0.02

One ticker, one call: quote + 1y technicals + expected move + regime + news catalysts. Replaces ~6 calls, priced below their sum

get_regime_forecast ⭐

$0.01

ML volatility-regime forecast + a transparent rules-based read (VIX bands, realized-vol percentile, trend)

get_track_record ⭐

$0.01

Normalized per-lane win rates + the server-side scored forecast ledger. Audit us before buying anything else

get_catalyst_radar ⭐

$0.01

Tickers with a fresh bullish news catalyst and why it matters — not scraped headlines

get_dip_radar ⭐

$0.01

Live dip scan over the exact 55-name book the trading system runs: RSI(2), distance from the 20-day high, tiered dip flags under disclosed thresholds

get_market_brief

$0.005

BTC/ETH/SOL + SPY/QQQ/DIA/IWM + crypto fear & greed, one call

get_trending

$0.005

StockTwits trending + r/wallstreetbets mention counts

get_movers

$0.005

Biggest US movers with live quotes, sorted by absolute move

get_expected_move

$0.005

Options-implied expected move (ATM straddle to nearest expiry), any symbol

get_macro

$0.003

Treasury yields (13w/5y/10y/30y), dollar index, gold, WTI crude, VIX

get_funding_rates

$0.003

BTC/ETH/SOL perp funding (8h + annualized), next funding time, mark price

get_ohlcv

$0.002

Daily OHLCV candles, any US symbol, 5d–1y

⭐ = unique to us, not repackaged vendor data.

The HTTP API carries more products than this server wraps — including narrow slices like /api/quote, /api/yields, /api/vix, /api/commodities, /api/crypto-spot, /api/etf-quotes, /api/wsb-mentions and /api/stocktwits-trending, plus a free full-sample response at /api/sample. See the manifest or openapi.json.

Related MCP server: x402-api

Setup

Paid tools need a small dedicated Base wallet holding USDC (a few dollars goes a very long way at these prices). Use a burner wallet, never your main one.

{
  "mcpServers": {
    "orchard-data": {
      "command": "npx",
      "args": ["-y", "orchard-data-mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x<burner wallet private key>" }
    }
  }
}

Without EVM_PRIVATE_KEY the three free tools still work, and the paid tools explain what they would cost rather than failing silently.

How payment works

Each paid tool call: GET → HTTP 402 with payment requirements → the client signs a USDC transfer authorization with your key → retries with the payment header → JSON. Settlement is gasless for the buyer (EIP-3009 via the x402 facilitator). Verified end-to-end on Base mainnet.

Available Tools

1 tool
get_catalyst_radarA

Tickers with fresh bullish news catalysts ($0.01), from an AI news scanner feeding a live trading system. Refreshed ~15min during US market hours.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it discloses the refresh frequency (~15min during US market hours) and source (AI news scanner). It does not mention rate limits or auth needs, but for a read-only tool this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no extraneous information. The key facts are front-loaded, and every word adds value. Perfectly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description provides reasonable expectations: tickers with bullish catalysts and refresh timing. It could mention output format (e.g., list), but is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so baseline is 4. The description adds no parameter details, which is appropriate given the empty input schema and 100% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it provides tickers with fresh bullish news catalysts, making the tool's purpose immediately obvious. The verb 'get' and resource 'catalyst radar' are explicitly defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, though no sibling tools exist. The description implies use during US market hours due to refresh timing, but lacks explicit when-to-use or when-not-to-use context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.1.2
    • First observedget_catalyst_radar
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools.

Naming Consistency5/5

Single tool adheres to a clear verb_noun pattern (get_catalyst_radar).

Tool Count3/5

With only one tool, the server's scope is very narrow; while it may be sufficient for a single purpose, it feels thin compared to typical MCP servers.

Completeness5/5

For the stated purpose of providing AI-scanned bullish news catalysts, a single retrieval tool is complete; no obvious gaps in functionality.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • market-data-mcp

    SmashToes
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    Real-time financial market data MCP server. Stocks, crypto, technicals, sentiment, FDA calendar. No API keys required.
    -

  • x402-api

    fernsugi
    A
    license
    A
    quality
    D
    maintenance
    MCP server for pay-per-call DeFi and crypto data via x402 micropayments on Base. 8 endpoints: token prices, TVL, funding rates, token security, gas tracker, whale monitoring, wallet profiling, and yield scanning.
    8
    51
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/letom1176-spec/orchard-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server