Is hunterkiller live?

Yes — it answered the hub's last check (checked 27m ago). It answered 100% of checks over the last 30 days.

Is hunterkiller free to use?

Partly — some of its tools are open, others need a key or payment.

What tools does hunterkiller have?

18 tools: buy_credits, feedback, desk_read, get_magnet_levels_teaser, get_reach_stats, prepare_trade, list_symbols, get_feed_trust, ….

Is hunterkiller 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.

_ registry / mcp + a2a streamable-http · checked 27m ago

hunterkiller

https://hunterkiller.io

Registry code: deacfef2b4c8cfde

api record

Validated crypto-liquidation intelligence: calibrated magnets, walk-forward reach, feed-trust reconciliation, accuracy proof. Every tool response carries an honesty envelope (basis, as-of, sample-n discipline) — all outputs are descriptive, NOT forecasts. Access: the DATA TOOLS require a B2B API key (Bearer or x-api-key, metered identically to the REST /api/v1 API; self-serve at /api/keys/mine). Keyless clients get protocol discovery plus three free teasers (get_proof_summary, get_magnet_levels_teaser, get_feed_trust_summary), all built only from surfaces the public website already publishes.

endpoint: https://hunterkiller.io/mcp
door code: a98dbf0d4d567a3a
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 hunterkiller live?: Yes — it answered the hub's last check (checked 27m ago). It answered 100% of checks over the last 30 days.
Is hunterkiller free to use?: Partly — some of its tools are open, others need a key or payment.
What tools does hunterkiller have?: 18 tools: buy_credits, feedback, desk_read, get_magnet_levels_teaser, get_reach_stats, prepare_trade, list_symbols, get_feed_trust, ….
Is hunterkiller 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

877ms

last good check

priced tools

of 18 tools

_ answered our checks, 90 days 2 checks · signed record

2026-11-07 20:55 unknown → live
2026-11-07 20:55 unknown → live

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 18 tools

1 open1 auth-required 16 never probed 2 of 18 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.

get_feed_trust_summary open 27m ago
FREE (keyless). Summary of the public feed-trust reconciliation audit: per-venue verdicts on OUR OWN liquidation feed with match rate, coverage and assessable-run n — the same fields hunterkiller.io/proof/feed_trust publishes. A descriptive audit of data quality, not a trading signal.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
get_accuracy_proof auth-required 27m ago
API KEY REQUIRED. The published accuracy-proof aggregate (the same payload as the public /proof/stats): walk-forward precision with n, baselines, and window. Descriptive track record, not a forecast.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
buy_credits unknown never probed
API KEY REQUIRED (a free key works). Buy prepaid live Desk Read calls with a card: returns a Stripe Checkout URL to hand to your human. Packs: p10 ($10, 600 calls), p50 ($50, 3500), p200 ($200, 16000). With credits a free key gets live Desk Read, one credit per call. Balance: GET /api/agents/credits. This is a purchase action, not a trading signal.

mcp-tool
{ "type": "object", "required": [ "pack_id" ], "properties": { "pack_id": { "enum": [ "p10", "p50", "p200" ], "type": "string" }, "return_url": { "type": "string", "description": "Optional hunterkiller.io URL to return to." } } }
arguments 20 lines

feedback unknown never probed

FREE, no key needed. Tell us what you needed and did not get; a human and our agents read every item. Missing field, wrong shape, unclear verdict, symbol we lack, latency, price: say it plainly. Max 2 KB, 5 items per hour per address. Never include keys or secrets; items that look like secrets are refused. Service feedback, not a trading signal.

mcp-tool

{
  "type": "object",
  "required": [
    "need"
  ],
  "properties": {
    "need": {
      "type": "string",
      "description": "What you needed and did not get (required)."
    },
    "tool": {
      "type": "string",
      "description": "Optional. The tool or endpoint this is about."
    },
    "symbol": {
      "type": "string",
      "description": "Optional. Perp pair this is about."
    },
    "contact": {
      "type": "string",
      "description": "Optional. Where a human can reply."
    },
    "context": {
      "type": "string",
      "description": "Optional. What you were trying to do."
    }
  }
}

arguments 28 lines

desk_read unknown never probed
FREE delayed keyless, live with paid access. Descriptive liquidation walls, cascade path, crowd and position distance, plus lines[] and text. GET /api/desk_read/symbols lists coverage. Unknown symbols return unknown_symbol and invalid numbers return invalid_number, with isError:true; live-only symbols on the free tier return symbol_requires_live_access with the free set in did_you_mean. The deprecated compatibility field verdict is wall_in_band, no_wall_in_band or thin_data, never null; proceed, reduce and skip are no longer emitted (contract change, SDK 0.4.1 docs). wall_in_band means the nearest wall on either side is under 1 percent from price, the same distance as flags.liq_distance_pct and the same test as flags.wall_within_1pct; thin_data means no price or no wall data. verdict_long and verdict_short apply that test to the losing-side wall (below for a long, above for a short) at the current price and assumed_leverage, or for your position. confidence is null with confidence_basis unscored until the public ledger scores verdicts. Compatibility metadata includes verdict_side, verdict_long, verdict_short, verdict_other, bias and confidence. The verdict, stop and target fields are deprecated compatibility fields, never advice. verdict is descriptive (wall_in_band, no_wall_in_band or thin_data) and reads the same wall set as the descriptive flags liq_distance_pct, wall_within_1pct and crowd_aligned, which replace it. stop_suggestion and target_suggestion mirror the deprecated plan and render on no customer surface.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "ref": { "type": "string", "description": "Optional. Attribution tag." }, "lang": { "enum": [ "en", "zh", "ja", "ko", "es", "pt" ], "type": "string", "description": "Optional. Language of lines, text and act_label. Default en." }, "side": { "enum": [ "long", "short" ], "type": "string", "description": "Optional. Your position side." }, "entry": { "type": "number", "description": "Optional. Your entry price." }, "symbol": { "type": "string", "description": "e.g. BTCUSDT" }, "leverage": { "type": "number", "description": "Optional. Your leverage." } } }
arguments 44 lines
get_magnet_levels_teaser unknown never probed
FREE (keyless). BTC/ETH liquidation-cluster teaser: the top-3 strongest clusters per side (short-liq fuel above price, long-liq below) — the same published teaser data the anonymous free map and the public /learn pages serve, with the free-tier delay/scrub applied by construction. Descriptive positioning context, not a forecast. The full graded ladder (every level with reach-rate + n + CI, real-time, full symbol universe) requires an API key.

mcp-tool
{ "type": "object", "properties": { "symbol": { "type": "string", "description": "Optional: BTCUSDT or ETHUSDT (the free-teaser majors). Omit for both." } } }
arguments 9 lines
get_reach_stats unknown never probed
API KEY REQUIRED. Walk-forward horizon reach probabilities for one symbol (out-of-sample backtest record): per-horizon up/down band reach with n + 95% CI. Descriptive history, not a forecast.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "description": "Perp symbol, e.g. ETHUSDT." } } }
arguments 12 lines

prepare_trade unknown never probed

API KEY REQUIRED. Calculate position quantity, notional and optional gross reward-to-risk from user-supplied levels, with a supporting decision packet. Fees, funding and slippage are explicitly excluded. Descriptive preparation, not a forecast. Never signs or executes.

mcp-tool

{
  "type": "object",
  "required": [
    "symbol",
    "direction",
    "entry",
    "invalidation",
    "risk_usd"
  ],
  "properties": {
    "entry": {
      "type": "number",
      "exclusiveMinimum": 0
    },
    "symbol": {
      "type": "string"
    },
    "target": {
      "type": "number",
      "exclusiveMinimum": 0
    },
    "risk_usd": {
      "type": "number",
      "exclusiveMinimum": 0
    },
    "direction": {
      "enum": [
        "long",
        "short"
      ],
      "type": "string"
    },
    "invalidation": {
      "type": "number",
      "exclusiveMinimum": 0
    }
  }
}

arguments 38 lines

list_symbols unknown never probed
API KEY REQUIRED. The serveable perp symbol universe (the positive allowlist) — the same list as keyed REST GET /api/v1/symbols. Coverage metadata — descriptive, not a forecast.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
get_feed_trust unknown 27m ago
API KEY REQUIRED. Per-venue reconciliation verdicts for OUR OWN liquidation feed (rolling 7d): each venue's ingested events verified against an independent check, with assessable-run n shown. A descriptive audit of data quality, not a trading signal.

mcp-tool
{ "type": "object", "properties": { "venue": { "type": "string", "description": "Optional venue filter (e.g. binance, bybit, okx, deribit). Omit for all." } } }
arguments 9 lines
subscribe_events unknown never probed
Describe a protected Cascade Feed v2 SSE connection and recorded-event replay. wall_touched, wall_broken, cascade_live and oi_shock; source timestamps and opaque cursors. API key required, with its existing live or delayed entitlement. Returns connection_required, not an open socket; send the key in a header, never a URL. Descriptive, not a forecast.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "after": { "type": "string", "description": "Optional opaque, exclusive event cursor for this symbol and tier." }, "symbol": { "type": "string", "description": "Perpetual pair such as BTCUSDT." } }, "additionalProperties": false }
arguments 17 lines
get_liquidation_census unknown never probed
API KEY REQUIRED. Hyperliquid exact liquidation census for one symbol. Aggregate price bands with forced long and short notional, stated coverage of venue open interest, snapshot identity and data age. A free API key receives a stored delayed snapshot. Pro keys and prepaid credits receive the current snapshot. No account rows. Separate from estimated liquidation walls. Descriptive census, not a forecast.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string" } }, "additionalProperties": false }
arguments 12 lines
hk_levels unknown never probed
API KEY REQUIRED (a free key works). Liquidation levels for one coin: the same hk.levels.v1 payload as REST GET /api/v1/levels/{symbol} — the nearest wall above and below the mark, every wall with price, side, usd, signed distance_pct, first_seen_ts, age_hours and an evidence label (validated, measured or unmeasured), the snapshot as_of and age_sec, and the public record link. A free key reads the 2 hour delayed snapshot on the free coins (one prepaid credit buys a live coin); a paid key reads the current snapshot. Descriptive, not a forecast.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "description": "Perp symbol, e.g. BTCUSDT." } }, "additionalProperties": false }
arguments 13 lines
get_proof_summary unknown never probed
FREE (keyless). The public proof summary: headline walk-forward precision with sample n + confidence lower bound, venues measured, per-venue feed-trust verdicts, and evidence pointers — the same aggregate hunterkiller.io/proof serves. Nothing per-level. Descriptive, not a forecast.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
get_liquidation_magnets unknown never probed
API KEY REQUIRED. Calibrated liquidation magnets for one symbol: per-horizon walk-forward empirical reach-rate (reach probability with sample n + Wilson lower bound) plus the magnet density histogram. Measured out-of-sample; descriptive, not a forecast. Unvalidated horizons are withheld, never served as numbers.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "frame": { "type": "string", "description": "Optional horizon filter: 15m | 1h | 4h | 1D. Omit for all horizons." }, "symbol": { "type": "string", "description": "Perp symbol, e.g. BTCUSDT." } } }
arguments 16 lines
get_engine_read unknown never probed
API KEY REQUIRED. The full /engine_read payload for a symbol+horizon as served to non-owner customers: the descriptive engine read plus horizons_meta with the per-horizon lane label (empirical = a walk-forward-validated measured cell is serving; modeled = the honest-null legacy lane) and the strict per-horizon gate_validated flag. The layer recipe is scrubbed by the standard non-owner egress. A descriptive structure read, not a forecast.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "description": "Perp symbol, e.g. BTCUSDT." }, "horizon": { "type": "string", "description": "Optional: 1h | 4h | 24h | 168h | 720h (default 1h)." } } }
arguments 16 lines
get_proof_anchors unknown never probed
API KEY REQUIRED. The public projection of the daily proof-anchor chain: each anchor day's date + content digest + chain hash (the append-only tamper-evidence ledger for the accuracy track record), with the keyless chain-integrity verification recipe. HMAC signatures and the attestation key are NOT included. Verification metadata — descriptive, not a forecast.

mcp-tool
{ "type": "object", "properties": { "limit": { "type": "integer", "description": "Optional: how many of the most recent daily anchors to return (default 30, max 200)." } } }
arguments 9 lines
get_decision_packet unknown never probed
API KEY REQUIRED. One composite evidence packet for a symbol: validated liquidation magnets, historical reach, contagion, derived venue structure and feed trust. Components fail independently and report honest unavailable states. Descriptive evidence, not a forecast. No order is placed.

mcp-tool
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "description": "Perp symbol, e.g. BTCUSDT." } } }
arguments 12 lines

_ try it over mcp 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id deacfef2b4c8cfde.

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/deacfef2b4c8cfde/badge.svg)](https://brick.blue/agent/deacfef2b4c8cfde?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 knowoff the mcp door

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

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.

_ also on hunterkiller.io 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

agents.hunterkiller.io agents.hunterkiller.io mcp · 0 tools