Hunter Killer

io.github.Irishman-Management-LLCPublished by GitHub account Irishman-Management-LLCv1.0.0Updated Nov 7, 2026

Liquidation walls, snapshot age, evidence labels and a public record. Managed OAuth.

The publisher's own server: Hunter Lease

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant read-only crypto liquidation-wall measurements, snapshot age, evidence labels and a public record.

What you can do
  • Read liquidation walls and nearest levels for a coin pair, with snapshot age and evidence labels
  • Inspect tier, delay, timestamps and record fields, and keep them with any result shown
  • Use a managed OAuth transport, with a public apex endpoint offering discovery and teasers
  • Access read-only HTTP client wrappers and function schemas for LangChain, CrewAI, Composio and Node
When to use it
Useful when you want an assistant to pull descriptive crypto market-structure measurements (liquidation walls, level ladders, data freshness) into a chat or agent workflow, without any trading execution.
Requirements
A remote streamable HTTP endpoint; no local package or environment variables. Managed OAuth sign-in through the MCP client is required, and OAuth access is separate from any paid data entitlement. Calls may return 401, 403, 402, 429 or 503.
Before you install
Free data is described as 2 hours behind on six coins, and a first call can still return 401. OAuth access does not include paid data entitlement, and no payment is automatic. Results are descriptive measurements, not trading advice; paper strategy examples are simulations with historical proxy inputs, costs and losing periods, and live execution is disabled.

Installation

In SourceWeft

  1. Open Hunter Killer in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Irishman-Management-LLC%2Fhunterkiller/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "hunter-killer": {
      "type": "http",
      "url": "https://agents.hunterkiller.io/mcp"
    }
  }
}

README

Hunter Killer agent examples

sh
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.py and examples/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://agents.hunterkiller.io/mcp is the Managed OAuth transport. Complete its normal sign in flow in your MCP client. OAuth transport access and paid Hunter Killer data entitlement are separate. registry/server.json describes that hosted server, not an installable open source server implementation. The public apex https://hunterkiller.io/mcp also offers discovery and public teasers. See the current auth and tool details on the data door.

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.

Source: README.md at commit addd58f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Hunter integrations