_ registry / mcp streamable-http · checked 45m ago

io.github.lucrummediacompany/trading-zones

https://api.tradingzones.app

Registry code: a48fcbe346efd104

api record

Use discover_4h_setups first. For native MCP payment call get_btc_4h_setup, get_eth_4h_setup, get_xrp_4h_setup, get_ondo_4h_setup or get_tz_select_4h_setup. Retry PaymentRequired with _meta['x402/payment']. The prepare_* tools remain available as an HTTP purchase fallback. Open-source buyer SDK: https://github.com/lucrummediacompany/Komunikacja

endpoint
https://api.tradingzones.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is io.github.lucrummediacompany/trading-zones live?
Yes — it answered the hub's last check (checked 45m ago). It answered 100% of checks over the last 30 days.
Is io.github.lucrummediacompany/trading-zones free to use?
Yes — the hub reached it with no key and no payment.
What tools does io.github.lucrummediacompany/trading-zones have?
13 tools: get_eth_4h_setup, get_xrp_4h_setup, get_ondo_4h_setup, get_tz_select_4h_setup, discover_4h_setups, prepare_4h_setup_purchase, prepare_ondo_4h_purchase, get_btc_4h_setup, ….
Is io.github.lucrummediacompany/trading-zones safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
197ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 5 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
1

distinct

settlements
9

last 2026-10-23

received on chain
0.27 USDC

counted from three payers (thin, concentrated)

_ what it can do 13 tools
3 open 10 never probed 3 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • prepare_btc_4h_purchase open 45m ago

    Return the exact paid URL and wallet steps for the independent BTC 4H setup. No funds move until the wallet or user authorizes the x402 request.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • prepare_eth_4h_purchase open 45m ago

    Return the exact paid URL and wallet steps for the independent ETH 4H setup. No funds move until the wallet or user authorizes the x402 request.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_performance_evidence open 45m ago

    Read the current public live-simulation evidence for closed setups selected by Trading Zones Selector. The rate does not describe every non-selected market package.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_eth_4h_setup unknown never probed

    Purchase and return the complete current ETH 4H setup inside this MCP tool call. 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'].

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_xrp_4h_setup unknown never probed

    Purchase and return the complete current XRP 4H setup inside this MCP tool call. 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'].

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_ondo_4h_setup unknown never probed

    Purchase and return the complete current ONDO 4H setup inside this MCP tool call. 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'].

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_tz_select_4h_setup unknown never probed

    Purchase and return the complete current TZ SELECT 4H setup inside this MCP tool call. 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'].

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • discover_4h_setups unknown never probed

    List the four independently purchasable market setups and TZ SELECT, which selects at most one of those setups per 4H cycle.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • prepare_4h_setup_purchase unknown never probed

    Return the exact paid resource URL, price ceiling and wallet steps for one complete setup. The wallet-enabled agent signs and retries the returned HTTPS request; this tool never moves funds.

    mcp-tool

    {
  "type": "object",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "enum": [
        "BTC",
        "ETH",
        "XRP",
        "ONDO",
        "TZ-SELECT"
      ],
      "type": "string",
      "description": "BTC, ETH, XRP or ONDO, or TZ-SELECT for the selector's current choice."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • prepare_ondo_4h_purchase unknown never probed

    Return the exact paid URL and wallet steps for the independent ONDO 4H setup. No funds move until the wallet or user authorizes the x402 request.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_btc_4h_setup unknown never probed

    Purchase and return the complete current BTC 4H setup inside this MCP tool call. 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'].

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • prepare_xrp_4h_purchase unknown never probed

    Return the exact paid URL and wallet steps for the independent XRP 4H setup. No funds move until the wallet or user authorizes the x402 request.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • prepare_tz_select_4h_purchase unknown never probed

    Return the exact paid URL and wallet steps for the independent TZ SELECT 4H setup. No funds move until the wallet or user authorizes the x402 request.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a48fcbe346efd104.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a48fcbe346efd104/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a48fcbe346efd104/badge.svg)](https://brick.blue/agent/a48fcbe346efd104?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.