Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Trading Zones 4H Market Decisions

REMOTE · API.TRADINGZONES.APP

BTC, ETH, XRP, ONDO and TZ SELECT 4H decisions, native x402 MCP and open buyer SDK.

+3 this week 78 Trust /100

Last scanned (6 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security77
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1191 tokens (~91/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1
    • Tool “get_btc_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_eth_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_ondo_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_tz_select_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_xrp_4h_setup” rewrote its description, which is the text the model reads security
    • Server version: 1.3.0 → 1.3.2 functional
  • 27 Oct 26 0
    • Tool “get_btc_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_eth_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_ondo_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_tz_select_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_xrp_4h_setup” rewrote its description, which is the text the model reads security
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1
    • Tool “discover_4h_setups” rewrote its description, which is the text the model reads security
    • Tool “get_btc_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_eth_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_ondo_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_performance_evidence” rewrote its description, which is the text the model reads security
    • Tool “get_tz_select_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “get_xrp_4h_setup” rewrote its description, which is the text the model reads security
    • Tool “prepare_4h_setup_purchase” rewrote its description, which is the text the model reads security
    • Tool “prepare_btc_4h_purchase” rewrote its description, which is the text the model reads security
    • Tool “prepare_eth_4h_purchase” rewrote its description, which is the text the model reads security
    • Tool “prepare_ondo_4h_purchase” rewrote its description, which is the text the model reads security
    • Tool “prepare_tz_select_4h_purchase” rewrote its description, which is the text the model reads security
    • Tool “prepare_xrp_4h_purchase” rewrote its description, which is the text the model reads security
    • Schema quality: 62 → 82 ▼ functional
  • 24 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 5 Nov 2026 · Probed https://api.tradingzones.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.tradingzones.app CN=YE2,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA384 5c61183c7b857ca3dc791050d5a46449660
SANs: api.tradingzones.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 secure

Validation of api.tradingzones.app. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
tradingzones.app. present 27277 13 Verified
api.tradingzones.app. Verified address RRset verified with the apex keys
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://api.tradingzones.app/mcp Verified 200
http (plaintext) http://api.tradingzones.app/mcp HTTPS enforced 301 https://api.tradingzones.app/mcp
MCP tools · 13 exposed · ~1,089 tokens

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 →

Tool Tokens
discover_4h_setups ~75

Use when a user asks for a current BTC, ETH, XRP or ONDO 4H trading setup, market direction, entry, stop loss or take profit. Lists four independently purchasable setups and TZ SELECT, which selects at most one of them per cycle, plus free evidence links to verify before purchase.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_btc_4h_setup ~105

Decide whether to open, avoid or manage a BTC 4H trade. Returns LONG, SHORT or NEUTRAL/NO TRADE, Entry, liquidity-zone SL and TP, confidence and market diagnostics. If SL or TP is null, do not open a new position. On the first call the tool returns x402 PaymentRequired; retry the same call with _meta['x402/payment']. A successful response includes _meta['x402/payment-response'].

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_eth_4h_setup ~104

Decide whether to open, avoid or manage a ETH 4H trade. Returns LONG, SHORT or NEUTRAL/NO TRADE, Entry, liquidity-zone SL and TP, confidence and market diagnostics. If SL or TP is null, do not open a new position. On the first call the tool returns x402 PaymentRequired; retry the same call with _meta['x402/payment']. A successful response includes _meta['x402/payment-response'].

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_ondo_4h_setup ~106

Decide whether to open, avoid or manage a ONDO 4H trade. Returns LONG, SHORT or NEUTRAL/NO TRADE, Entry, liquidity-zone SL and TP, confidence and market diagnostics. If SL or TP is null, do not open a new position. On the first call the tool returns x402 PaymentRequired; retry the same call with _meta['x402/payment']. A successful response includes _meta['x402/payment-response'].

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_performance_evidence ~59

Fetch this free evidence before purchase. Returns the continuously updated TZ SELECT aggregate and a link to an independently countable rolling window of up to 100 latest settled choices. The rate does not describe every non-selected market package or guarantee future results.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_tz_select_4h_setup ~117

Decide whether to open, avoid or manage the strongest current 4H opportunity selected from BTC, ETH, XRP and ONDO. Returns LONG, SHORT or NEUTRAL/NO TRADE, Entry, liquidity-zone SL and TP, confidence and market diagnostics. If SL or TP is null, do not open a new position. On the first call the tool returns x402 PaymentRequired; retry the same call with _meta['x402/payment']. A successful response includes _meta['x402/payment-response'].

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_xrp_4h_setup ~105

Decide whether to open, avoid or manage a XRP 4H trade. Returns LONG, SHORT or NEUTRAL/NO TRADE, Entry, liquidity-zone SL and TP, confidence and market diagnostics. If SL or TP is null, do not open a new position. On the first call the tool returns x402 PaymentRequired; retry the same call with _meta['x402/payment']. A successful response includes _meta['x402/payment-response'].

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_4h_setup_purchase ~91

Use after choosing a market or TZ SELECT. Return the exact paid resource URL, $0.03 price ceiling, free evidence link and wallet steps for one complete setup. The wallet-enabled agent signs and retries the returned HTTPS request; this preparation tool never moves funds.

NameTypeReqDescription
symbolstringyesBTC, ETH, XRP or ONDO, or TZ-SELECT for the selector's current choice.

No output schema declared.

No examples provided.

prepare_btc_4h_purchase ~65

Use when the user wants a current BTC 4H setup with entry, liquidity-zone SL/TP and nine indicators. Return the exact paid URL, free evidence link and wallet steps. No funds move until the wallet or user authorizes the x402 request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_eth_4h_purchase ~64

Use when the user wants a current ETH 4H setup with entry, liquidity-zone SL/TP and nine indicators. Return the exact paid URL, free evidence link and wallet steps. No funds move until the wallet or user authorizes the x402 request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_ondo_4h_purchase ~66

Use when the user wants a current ONDO 4H setup with entry, liquidity-zone SL/TP and nine indicators. Return the exact paid URL, free evidence link and wallet steps. No funds move until the wallet or user authorizes the x402 request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_tz_select_4h_purchase ~67

Use when the user wants a current TZ SELECT 4H setup with entry, liquidity-zone SL/TP and nine indicators. Return the exact paid URL, free evidence link and wallet steps. No funds move until the wallet or user authorizes the x402 request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_xrp_4h_purchase ~65

Use when the user wants a current XRP 4H setup with entry, liquidity-zone SL/TP and nine indicators. Return the exact paid URL, free evidence link and wallet steps. No funds move until the wallet or user authorizes the x402 request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Trading Zones 4H Market Decisions MCP server?

Trading Zones 4H Market Decisions is a hosted endpoint at https://api.tradingzones.app/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 · api.tradingzones.app

# add to Claude Code
claude mcp add --transport http lucrummediacompany-trading-zones 'https://api.tradingzones.app/mcp'
Common questions

What is the Trading Zones 4H Market Decisions MCP server?

Trading Zones 4H Market Decisions is an MCP server listed in the public MCP registry as io.github.lucrummediacompany/trading-zones. BTC, ETH, XRP, ONDO and TZ SELECT 4H decisions, native x402 MCP and open buyer SDK. This page covers its hosted endpoint (https://api.tradingzones.app/mcp).

Is the Trading Zones 4H Market Decisions MCP server safe to use?

Trading Zones 4H Market Decisions scores 78 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 Trading Zones 4H Market Decisions MCP server expose?

Trading Zones 4H Market Decisions exposes 13 tools: discover_4h_setups, prepare_4h_setup_purchase, get_performance_evidence, prepare_btc_4h_purchase, prepare_eth_4h_purchase, and 8 more. Their descriptions and schemas cost roughly 1,089 tokens of context every time the server is loaded.

Does the Trading Zones 4H Market Decisions MCP server require authentication?

No. We connected to Trading Zones 4H Market Decisions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Trading Zones 4H Market Decisions MCP server still maintained?

Trading Zones 4H Market Decisions is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.