Is the Cabal Hunter MCP server down?

mcp-registry/com.cabal-hunter.api/cabal-hunter · v1.0.0

Also listed as awesome/paulf280-ui/solana-safe-sniper-mcp-template

As of 2026-10-24 18:50 UTC, the Cabal Hunter MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 4 minutes.

Solana pre-trade safety for AI agents: cabal, bundle, dump, deployer & honeypot in one verdict.

claude mcp add --transport http cabal-hunter-mcp-server https://api.cabal-hunter.com/mcp

{
  "mcpServers": {
    "cabal-hunter-mcp-server": {
      "type": "http",
      "url": "https://api.cabal-hunter.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

What to fix (3)

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.cabal-hunter.api%2Fcabal-hunter/fixes

{
  "name": "check_cabal_risk",
  "description": "Pre-trade safety check for any Solana token mint: is a buyer about to be\nsomeone's exit liquidity? Every wallet cluster carries its evidence_txs.\n\nAFTER YOU BUY: POST /api/watch {mint} with an X-API-Key (any key; add\nwebhook_url on the Pro plan) and we alert you the moment a coordinated dump\nor liquidity drain starts on that token — carrying the same on-chain\nevidence. This scan is a BUY check; a watch is a HOLD check, and a holder\nneeds the second one continuously. GET/DELETE /api/watch manage ",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "mintAddress"
    ],
    "properties": {
      "mintAddress": {
        "type": "string",
        "maxLength": 44,
        "minLength": 32,
        "description": "The Solana mint address of the token to audit (base58, 32–44 chars)"
      },
      "pairCreatedAt": {
        "type": "number",
        "description": "Optional: DexScreener pairCreatedAt timestamp in milliseconds. Speeds up analysis when provided."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "check_wallet_in_token",
  "description": "Is a SPECIFIC wallet involved in a SPECIFIC Solana token? Use this when a\nuser names a wallet they are worried about, or when your agent keeps its\nown watchlist of addresses and wants to screen a token against one.\n\nAnswers from two sources at once:\n  1. the traced holders of that token — rank, % of supply, buy slot,\n     whether it funded a coordinated cluster, whether it created the token,\n     or whether it is the liquidity pool / a labelled exchange wallet\n  2. a LIVE on-chain holding lookup",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "mintAddress",
      "wallet"
    ],
    "properties": {
      "wallet": {
        "type": "string",
        "maxLength": 44,
        "minLength": 32,
        "description": "The wallet address to look for in that token (base58, 32–44 chars)"
      },
      "mintAddress": {
        "type": "string",
        "maxLength": 44,
        "minLength": 32,
        "description": "The Solana mint address of the token (base58, 32–44 chars)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.cabal-hunter.api/cabal-hunter"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.cabal-hunter.api/cabal-hunter"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~556 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.87% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• check_cabal_risk ~278 tokens
• check_wallet_in_token ~278 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cabal-hunter.api%2Fcabal-hunter.svg)](https://glimind.com/server/mcp-registry%2Fcom.cabal-hunter.api%2Fcabal-hunter?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.cabal-hunter.api%2Fcabal-hunter?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cabal-hunter.api%2Fcabal-hunter.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cabal-hunter.api%2Fcabal-hunter.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.cabal-hunter.api%2Fcabal-hunter?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a655ccbdfbe77090…, first seen 2026-10-17, included at leaf 1334 of 60,556. Version history · verify what your client received.

Tools (2)

• check_cabal_risk
• check_wallet_in_token

Compare: most reliable security servers · most reliable finance servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Cabal Hunter MCP server down right now?

As of 2026-10-24 18:50 UTC, the Cabal Hunter MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Cabal Hunter MCP server provide?

Cabal Hunter MCP server advertises 2 tools, including check_cabal_risk, check_wallet_in_token.

How do I install Cabal Hunter MCP server?

Point your MCP client at this streamable-http endpoint: https://api.cabal-hunter.com/mcp

Is the Cabal Hunter MCP server safe to connect to an AI agent?

Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Cabal Hunter MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.