AI HUNTERZ — Autonomous Crypto Intelligence
REMOTE · AI-HUNTERZ-MCP.HUNTERZAI.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 20
49 crypto intelligence APIs. Whale tracking, DeFi yields, alpha signals. Pay in USDC on Base.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 538 tokens (~59/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the AI HUNTERZ — Autonomous Crypto Intelligence MCP server?
AI HUNTERZ — Autonomous Crypto Intelligence is a hosted endpoint at https://ai-hunterz-mcp.hunterzai.workers.dev/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai-hunterz-mcp.hunterzai.workers.dev
claude mcp add --transport http hunterzai16z-ai-hunterz 'https://ai-hunterz-mcp.hunterzai.workers.dev/'
{
"mcpServers": {
"hunterzai16z-ai-hunterz": {
"url": "https://ai-hunterz-mcp.hunterzai.workers.dev/"
}
}
} {
"servers": {
"hunterzai16z-ai-hunterz": {
"type": "http",
"url": "https://ai-hunterz-mcp.hunterzai.workers.dev/"
}
}
} [mcp_servers.hunterzai16z-ai-hunterz] url = "https://ai-hunterz-mcp.hunterzai.workers.dev/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hunterzai16z-ai-hunterz": {
"type": "remote",
"url": "https://ai-hunterz-mcp.hunterzai.workers.dev/",
"enabled": true
}
}
} openclaw mcp add hunterzai16z-ai-hunterz --url 'https://ai-hunterz-mcp.hunterzai.workers.dev/' --transport streamable-http
mcp_servers:
hunterzai16z-ai-hunterz:
url: "https://ai-hunterz-mcp.hunterzai.workers.dev/" {
"McpServers": {
"hunterzai16z-ai-hunterz": {
"Transport": "http",
"Url": "https://ai-hunterz-mcp.hunterzai.workers.dev/"
}
}
} assistant mcp add hunterzai16z-ai-hunterz -t streamable-http -u 'https://ai-hunterz-mcp.hunterzai.workers.dev/'
{
"mcpServers": {
"hunterzai16z-ai-hunterz": {
"type": "http",
"url": "https://ai-hunterz-mcp.hunterzai.workers.dev/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://ai-hunterz-mcp.hunterzai.workers.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hunterzai.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 61cb6bb2c978cc677184a0a532e1632dd3b |
| SANs: *.hunterzai.workers.dev, hunterzai.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai-hunterz-mcp.hunterzai.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-hunterz-mcp.hunterzai.workers.dev | Verified | 200 | |
| http (plaintext) | http://ai-hunterz-mcp.hunterzai.workers.dev | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_reputation ~53
Get credit score for any wallet — human or AI agent. First-ever on-chain reputation scoring system. Price: $75/call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to score (0x...) |
No output schema declared.
No examples provided.
alpha_signals ~53
Get DeFi alpha opportunities — airdrops, yield farms, protocol incentives from DeFiLlama. Price: $0.10/call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain to focus on |
No output schema declared.
No examples provided.
dark_pool_decoder ~41
Decode institutional dark pool and hidden trading signals. Cross-references block settlements, bridge flows, and options activity. Price: $500/call via x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
defi_yields ~64
Get best DeFi yield opportunities ranked by APY, risk, and sustainability. Price: $0.10/call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| risk | string | – | Risk level: low, medium, high |
| token | string | – | Token to find yields for |
No output schema declared.
No examples provided.
hack_detector ~70
Scan any wallet for security threats — unlimited approvals, honeypots, rug pull signals, bot drainer patterns. Price: $25/call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum wallet address to scan (0x...) |
| chain | string | – | Chain to check: ethereum or base |
No output schema declared.
No examples provided.
liquidation_predictor ~62
Predict DeFi liquidations before they happen. Monitors Aave, Compound, MakerDAO positions within 10% of threshold. Price: $150/call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Token to focus on: ETH, BTC, etc. |
No output schema declared.
No examples provided.
non_human_oracle ~54
Detect and score AI agent wallets on-chain. World's first endpoint tracking machine vs human wallet activity. Price: $200/call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain to analyze: ethereum or base |
No output schema declared.
No examples provided.
pre_narrative_detector ~49
Detect crypto narratives 2-3 hours before Twitter and Telegram. Cross-references GitHub commits, TVL spikes, and whale patterns. Price: $100/call via x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whale_alerts ~67
Get real-time whale movements on Ethereum or Base. Detects $50K+ USDC transfers with AI-analyzed BULLISH/BEARISH signals. Price: $0.003/call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain to monitor: ethereum or base |
No output schema declared.
No examples provided.
What is the AI HUNTERZ — Autonomous Crypto Intelligence MCP server?
AI HUNTERZ — Autonomous Crypto Intelligence is an MCP server listed in the public MCP registry as io.github.hunterzai16z/ai-hunterz. 49 crypto intelligence APIs. Whale tracking, DeFi yields, alpha signals. Pay in USDC on Base. This page covers its hosted endpoint (https://ai-hunterz-mcp.hunterzai.workers.dev).
Is the AI HUNTERZ — Autonomous Crypto Intelligence MCP server safe to use?
AI HUNTERZ — Autonomous Crypto Intelligence scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI HUNTERZ — Autonomous Crypto Intelligence MCP server expose?
AI HUNTERZ — Autonomous Crypto Intelligence exposes 9 tools: whale_alerts, hack_detector, dark_pool_decoder, liquidation_predictor, non_human_oracle, and 4 more. Their descriptions and schemas cost roughly 513 tokens of context every time the server is loaded.
Does the AI HUNTERZ — Autonomous Crypto Intelligence MCP server require authentication?
No. We connected to AI HUNTERZ — Autonomous Crypto Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI HUNTERZ — Autonomous Crypto Intelligence MCP server still maintained?
AI HUNTERZ — Autonomous Crypto Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.