Analytics
hunterkiller.io
Provides cryptocurrency market analytics, including liquidation magnets and proof-of-reserves summaries, via free and API-key endpoints.
ENDPOINT 1
https://hunterkiller.io/mcp
MCP server metadata
- Name
- hunterkiller
- Version
- 1.2.0
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.
Known tools 12
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.hunterkiller]
url = "https://hunterkiller.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"hunterkiller": {
"type": "http",
"url": "https://hunterkiller.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: hunterkiller
Remote MCP URL: https://hunterkiller.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"hunterkiller": {
"url": "https://hunterkiller.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"hunterkiller": {
"type": "http",
"url": "https://hunterkiller.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "hunterkiller",
"transport": "streamable-http",
"url": "https://hunterkiller.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.