Remote MCP · Endpoint
com.cabal-hunter.api/cabal-hunter MCP server
No. com.cabal-hunter.api/cabal-hunter answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.cabal-hunter.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.cabal-hunter.api/cabal-hunter
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 310 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Solana pre-trade safety for AI agents: cabal, bundle, dump, deployer & honeypot in one verdict.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 310 ms |
| 2 days ago | Handshake completed | 312 ms |
| 4 days ago | Handshake completed | 335 ms |
| 5 days ago | Handshake completed | 300 ms |
| 7 days ago | Handshake completed | 315 ms |
| 8 days ago | Handshake completed | 324 ms |
| 9 days ago | Handshake completed | 368 ms |
| 12 days ago | Handshake completed | 332 ms |
| 13 days ago | Handshake completed | 325 ms |
| 15 days ago | Handshake completed | 317 ms |
| 16 days ago | Handshake completed | 322 ms |
| 17 days ago | Handshake completed | 304 ms |
| 18 days ago | Handshake completed | 324 ms |
| 19 days ago | Handshake completed | 308 ms |
| 20 days ago | Handshake completed | 303 ms |
| 21 days ago | Handshake completed | 360 ms |
| 22 days ago | Handshake completed | 295 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with com.cabal-hunter.api/cabal-hunter and makes no claim about it beyond what these checks measured.