HoneyLabs
MCP serverSearchThis app gives your AI access to honeypot probe data collected from decoy systems that record who tries to break in. Once added, your AI can look up an IP address and report its reputation, whether it has been seen scanning, and the fingerprints it left behind. That helps you judge whether a visitor, login attempt, or connected system looks risky before you act on it.
Available today. Use it from your connected AI after setup.
Needs your own account with this service. Credentials stay encrypted.
After adding it, ask your AI to look up a specific IP address and it will pull the related honeypot records.
Then ask your AI: use HoneyLabs to search events tool
What your AI can do with it
- Check the reputation of any IP address
- See whether an IP has been caught scanning honeypots
- Find out if an IP probes for known vulnerabilities
- Look up TLS and SSH fingerprints observed from an IP
From the project's README
As published by honeylabshq/honeylabs-mcp in README.md.
Honeypot threat intelligence as MCP tools. Query 90 days of probe data from our honeypot sensor network: IP reputation, scanner classification, CVE probing trends, TLS/SSH fingerprints (JA4, JA3, JA4H, HASSH), mTLS client certificates, Community ID flow hashes, and attack timelines. Use it straight from Claude, Cursor, Gemini, Cline, or any other Model Context Protocol client.
- 🌐 Web: https://honeylabs.net
- 🔌 MCP endpoint: https://mcp.honeylabs.net/mcp (streamable HTTP)
- 🧰 Tool catalog & worked prompts: https://honeylabs.net/mcp
- 📖 Docs: https://honeylabs.net/docs
- 🔑 Access: free with a key, within fair-use limits
Install
Claude Code
claude mcp add honeylabs \
--transport http \
https://mcp.honeylabs.net/mcp \
--header "Authorization: Bearer <your-key>"
Get a key at https://honeylabs.net/dashboard (magic-link sign-in, no password).
Claude Desktop / Cursor
Add to your MCP config:
{
"mcpServers": {
"honeylabs": {
"url": "https://mcp.honeylabs.net/mcp",
"headers": {
"Authorization": "Bearer <your-key>"
}
}
}
}
Cline
Same JSON config as Claude Desktop / Cursor. Install via the MCP Marketplace listing or paste the config block above into your settings.
Gemini CLI
gemini /mcp add honeylabs https://mcp.honeylabs.net/mcp
gemini /mcp auth honeylabs # OAuth flow, no static key
OAuth 2.1 with PKCE + DCR is supported at /oauth/authorize. Any MCP
client that speaks standard OAuth (Gemini, MCP Inspector, Smithery,
Cline's OAuth flow) works out of the box.
Tools
| Tool | What it answers |
|---|---|
ioc_lookup | Is this IP / domain known to be probing? Returns our verdict, whether it is a recognised benign scanner, the CVEs it probed, plus ports / paths / fingerprints. |
top_attackers | Ranked leaderboard of source IPs, ASNs, countries, ports, user-agents, or CVEs (by='cve') over a time window. |
search_events | Raw honeypot events matching filters (IP, ASN, country, dest_port, protocol, http_method, ja4/ja3, community_id, has_client_cert). |
attack_timeline | Hourly / daily attack volume over a window, with protocol / country / port filters. |
asn_enrich | Full profile for an ASN: total events, unique IPs, top ports, source countries, user-agents, org name. |
fingerprint_search | Search by TLS JA4 / JA3 / HTTP JA4H / SSH HASSH fingerprint to find shared infrastructure. |
cve_lookup | Who is probing a named CVE: severity, KEV status, top probing IPs with ASN and scanner tag, fingerprints, sample paths, daily timeline. |
payload_search | Full-text URL-path + user-agent search across attack traffic. |
Every tool is free to call. Plans differ by how much you can pull, not by which tools exist: each row in a response counts as one credit, and a free key gives 500 credits a day, with higher limits for heavier use. See https://honeylabs.net/docs#plans for the breakdown.
What the data is
HoneyLabs runs a fleet of honeypots that get probed by the public
internet all day. Every probe, meaning every connection, TLS
handshake, and HTTP request, is logged with the source IP, ASN,
geo, TLS/HTTP/SSH fingerprints, and full URL path. We retain the
last 90 days and expose it through this MCP server, a JSON API, a
public lookup web UI at /lookup/<ip>, and CSV / STIX exports.
This is our own ground-truth record of what is actively scanning the internet right now, gathered first-hand rather than copied from a CVSS database or a third-party reputation feed.
Showcase prompts
Things to ask Claude / Cursor / Gemini once HoneyLabs is wired in:
- "Is 80.82.77.202 a known scanner? When was it last seen and what does it probe?"
- "Pull every IP that hit port 445 with a non-Windows User-Agent in the last 24 hours."
- "Show CVE-2024-4577 probing volume per day for the last 7 days, broken down by ASN."
- "Which CVEs are being mass-scanned this week, and who is behind the top one?"
- "167.94.146.63 is hammering my firewall logs. Is that an attack or a research scanner?"
- "For the top 10 attackers on port 6379 right now, what TLS JA4 fingerprints do they share?"
More worked examples at https://honeylabs.net/mcp.
Open source
The honeypot fleet itself (Spip-Go) and the enrichment pipeline (Loom) are public. This repo (the MCP / API surface) is closed.
Contact
Tools it offers (9)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
search_events_tooltop_attackers_toolioc_lookup_toolcve_lookup_toolpayload_search_toolattack_timeline_toolasn_enrich_toolfingerprint_search_toolfingerprint_population_tool
Signals
- GitHub stars
- 2
- Last commit
- Sep 2026
Advanced
- Delivery
- mcp MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
net-honeylabs-mcp- Source
- github.com/honeylabshq/honeylabs-mcp
- Hosted endpoint
https://mcp.honeylabs.net/mcp