About Hunter Killer
Hunter Killer exposes cryptocurrency liquidation levels and supporting metadata for agent integrations and market-data users. Its public MCP endpoint offers discovery and level lookup for six free coins; the data is delayed, and trading examples use paper orders only.
Key features
- 01Liquidation walls and levels
- 02Snapshot age and evidence labels
- 03Public symbol discovery
- 04Read-only HTTP endpoint
- 05LangChain and CrewAI wrappers
- 06Paper-trading examples
Use cases
- 01Inspect liquidation levels with their age
- 02Pass market data to agent integrations
- 03Test strategy examples with paper orders
MCP support
The public endpoint at `https://hunterkiller.io/mcp` provides discovery, `list_symbols` and `hk_levels` without a key for six free coins, with a two-hour delay. A separate OAuth transport at `https://agents.hunterkiller.io/mcp` provides access to live tools; OAuth access and paid data entitlement are separate.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://hunterkiller.io/mcpclaude mcp add --transport http irishman-management-llc-hunterkiller https://hunterkiller.io/mcp{"mcpServers":{"irishman-management-llc-hunterkiller":{"type":"http","url":"https://hunterkiller.io/mcp"}}}Open in Cursor{"servers":{"irishman-management-llc-hunterkiller":{"type":"http","url":"https://hunterkiller.io/mcp"}}}Open in VS Code{"mcpServers":{"irishman-management-llc-hunterkiller":{"type":"http","url":"https://hunterkiller.io/mcp"}}}{"mcpServers":{"irishman-management-llc-hunterkiller":{"serverUrl":"https://hunterkiller.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEHunter Killer agent examples
curl --fail-with-body --max-time 20 https://hunterkiller.io/api/v1/levels/BTCUSDT
# Or, with only Python's standard library:
python3 examples/one_call.py BTCUSDT
The keyless rollout and wrapper publication are pending a live receipt. A first call can still return 401. A failure is never labeled as successful data. No external paying use is claimed.
Read liquidation walls, snapshot age, evidence labels and a public record. The strategy examples use paper orders. Live execution is disabled. Descriptive measurements, not trading advice.
Free data is 2 hours behind on six coins. Inspect tier, delay_sec,
as_of_iso, age_sec, nearest, walls, truth and record. Keep these
fields with any result you show. An empty ladder is not a trading instruction.
Calls can return 401, 403, 402, 429 or 503; errors must reach the caller.
Internal verification must use python3 examples/one_call.py --probe so probes
are not confused with external adoption.
Integrations
packages/langchain:hunterkiller-langchain, Python transport and LangChain factory.packages/crewai:hunterkiller-crewai, CrewAI factory using the same transport.packages/composio:hunterkiller-composio, experimental standalone session tool.packages/npm:hunterkiller-agent-tools, Node client, LangChain factory and function definitions.schemas/openai-function.json: strict Responses API function schema. Dispatch to the read only HTTP client.schemas/composio-openapi.json: public REST definition for custom bindings, not a hosted catalog listing.space: manual Gradio ladder demo for Hugging Face Spaces.examples/sdk.pyandexamples/sdk.mjs: existing published SDK Desk Read examples.examples/freqtrade: the Freqtrade paper strategy, native historical public wall proxy table and API key signup link.examples/hummingbot: the Hummingbot paper grid and its labeled historical quote model table.strategies: shared point in time inputs, sealed observations, full results, costs and losses.
The wrappers call the public endpoint directly because the versions of the
existing SDKs currently on PyPI and npm do not expose levels. They do not
compute walls or grades. Credentials, if supplied by the application, never
appear in the model's argument schema. No payment is automatic.
MCP
https://hunterkiller.io/mcp is the public door. Discovery, list_symbols
and hk_levels need no key for the six Free coins, 2 hours behind. REST and
these two tools share 60 requests per minute and 500 per UTC day per IP.
Response headers state the actual limit and quota mode. Directory health
checks that do not authenticate use this public apex URL.
https://agents.hunterkiller.io/mcp is the Managed OAuth transport for live
tools. Complete its normal sign in flow in your MCP client. OAuth transport
access and paid Hunter Killer data entitlement are separate. The protected
apex twin /mcp/protected retains the same gate. registry/server.json
version 1.0.1 lists the public apex first and the OAuth remote second; it
is hosted metadata, not an installable open source server implementation.
Public source and risk
Agent door, proof, privacy, risk. Never infer a future return or trade recommendation from these measurements. The paper examples retain their historical proxy inputs, costs and losing periods. Those results describe a simulation, not live performance.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.