{"id":"net.honeylabs/mcp","slug":"net-honeylabs-mcp","title":"HoneyLabs","description":"Honeypot probe data: IP reputation, scanners, CVE probing, TLS and SSH fingerprints.","version":"1.2.0","publisher":{"kind":"domain","id":"honeylabs.net","label":"honeylabs.net","url":"https://honeylabs.net"},"website":"https://honeylabs.net","repository":"https://github.com/honeylabshq/honeylabs-mcp","remotes":[{"type":"streamable-http","url":"https://mcp.honeylabs.net/mcp","headers":[{"description":"Bearer <hlk_…> API key from https://honeylabs.net/dashboard. Clients that support OAuth 2.1 need no key: the server advertises Dynamic Client Registration via WWW-Authenticate and /.well-known/oauth-protected-resource.","isRequired":true,"isSecret":true,"name":"Authorization"}]}],"packages":[],"published":"2026-10-29","updated":"2026-10-29","status":"online","auth":"","latency_ms":1450,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search_events_tool","title":"Search raw events","description":"Individual honeypot events with every field, newest first, filtered by source,\nnetwork, port, protocol or fingerprint.\n\nUse when the user wants to see the records themselves: \"show me the events from\nthis IP\", \"what hit port 443 yesterday\", \"every request carrying this JA4\",\n\"all RDP traffic regardless of port\". Do not use it to judge one address (use\nioc_lookup_tool), to rank or count (use top_at","read_only":true},{"name":"top_attackers_tool","title":"Rank sources, ports or CVEs","description":"Ranked leaderboard over a time window: the top source addresses, networks,\ncountries, destination ports, user agents, JA4 fingerprints, URL paths, reverse\nDNS domains or CVEs by event count.\n\nUse for \"who is attacking the most\", \"top countries hitting port 22\", \"most\ntargeted ports this week\", \"top networks by volume\", and with by='cve' for\n\"which CVEs are being scanned for right now\". Do not use ","read_only":true},{"name":"ioc_lookup_tool","title":"Look up an address, range or domain","description":"Everything the sensors hold on one IP address, a CIDR range, several ranges at\nonce, or a domain, with our verdict and the reasons for it. Start here for any\nquestion about a specific indicator.\n\nUse for \"is this IP malicious\", \"is this a known scanner\", \"have you seen this\naddress\", \"when was it last seen\", \"have any of this vendor's ranges touched\nyou\". Do not use it to rank many sources (use to","read_only":true},{"name":"cve_lookup_tool","title":"Who is probing a CVE","description":"Who is probing one named CVE, and how: counts, top probing addresses, networks,\ncountries, fingerprints, sample request paths and a daily timeline.\n\nUse whenever the user names a CVE: \"is CVE-2024-4577 being exploited in the\nwild\", \"who scans for CVE-2023-1389\", \"has anyone probed this before it was\npublished\". Do not pass a CVE id to payload_search_tool: the id is our label\nfor a detection patter","read_only":true},{"name":"payload_search_tool","title":"Search request text","description":"Literal substring search, ignoring case, over captured request text: URL path,\nrequest body, request headers and event summary.\n\nUse for \"find requests to /wp-admin\", \"which requests carried this user agent\nstring\", \"who sent '../../etc/passwd' last week\". It matches text that\nappeared in the request and nothing else, so these return nothing:\n  - a CVE id ('CVE-2024-4577'). Use cve_lookup_tool; th","read_only":true},{"name":"attack_timeline_tool","title":"Event volume over time","description":"Event counts over time, in hourly or daily buckets, optionally filtered by\nprotocol, country or destination port.\n\nUse for \"show the trend this week\", \"was there a spike on port 22\", \"how has\nSSH scanning changed over 30 days\". Do not use it to find who caused a spike\n(follow up with top_attackers_tool on the same window and filter) or to see\nthe events themselves (use search_events_tool).\n\nbucket","read_only":true},{"name":"asn_enrich_tool","title":"Profile a network (ASN)","description":"Profile of one autonomous system (a hosting provider, ISP or company network)\nover a time window: total events, unique addresses, top targeted ports, source\ncountries, top user agents and the organisation name.\n\nUse for \"tell me about AS202425\", \"what is this hosting provider doing\", \"is\nthis network a source of scanning\". To attribute one address to its network,\nioc_lookup_tool already returns th","read_only":true},{"name":"fingerprint_search_tool","title":"Find activity by fingerprint","description":"Events and sources that carried one client fingerprint in a time window.\n\nUse for \"have you seen this JA4\", \"which IPs share this TLS fingerprint\",\n\"find every scanner with this SSH client fingerprint\". For how widespread a\nfingerprint is and whether it is one operation or a common client, use\nfingerprint_population_tool. For HTTP request shapes a few headers away from an\nAkin fingerprint, use fin","read_only":true},{"name":"fingerprint_similar_tool","title":"Similar HTTP request shapes","description":"HTTP request shapes within a few headers of one Akin fingerprint, with what\nthose clients request and call themselves, and the family the fingerprint\nbelongs to.\n\nUse when an unfamiliar request shape turns up in your own web server, WAF or\nproxy logs and you want to know whether it is a known tool or a variant of\none: \"what is close to this fingerprint\", \"is this the same scanner with one\nheader a","read_only":true},{"name":"fingerprint_population_tool","title":"Who carries a fingerprint","description":"The population behind one client fingerprint over the full retained window:\nhow many source addresses carry it, across how many networks and countries,\nthe ports they hit, the top networks, a sample of addresses, and a read on its\nshape.\n\nUse for \"is this JA4 one botnet or a common tool\", \"how many networks use this\nHASSH\", \"how concentrated is this fingerprint\". The concentration field says\nconce","read_only":true},{"name":"udp_activity_tool","title":"UDP probes: DNS, QUIC and more","description":"UDP datagrams sent to the sensors: DNS questions, QUIC client fingerprints and\nother UDP probes, with the ports, networks and countries involved.\n\nUse for \"who is sending DNS ANY queries\", \"is anyone querying version.bind\",\n\"have you seen this QUIC JA4\", \"which UDP ports are probed\", \"what hits\n5060/udp\". Every other tool reads TCP only, so UDP questions belong here. A\nUDP source address can be fo","read_only":true},{"name":"interactive_credentials_tool","title":"Logins tried on interactive sensors","description":"Plaintext logins captured by the interactive sensors (sensors that answer as a\nreal service and hold the session): username, password, the service they were\ntried on, the outcome and the source address, newest first, plus the pairs\ntried most and a per-service breakdown.\n\nUse for \"what passwords are attackers trying on SSH\", \"which credentials did\nthis IP try\", \"what logins hit MySQL this week\". F","read_only":true},{"name":"interactive_files_tool","title":"Files handed to interactive sensors","description":"Files clients handed to the interactive sensors: uploads, mail attachments,\npublished messages and other artifacts, by SHA-256, with name, size, MIME\ntype, the sessions that carried them and the VirusTotal verdict when one is\nknown.\n\nUse for \"have you seen this hash\", \"what files did this IP upload\", \"which\nmalware samples reached the honeypots this month\". For files referenced by\nURL in exploit p","read_only":true},{"name":"interactive_sessions_tool","title":"Sessions held by one source","description":"Sessions one address or range held with the interactive sensors: when, which\nport and protocol, the service the sensor answered as, the session verdict\n(scan, credential or exploit), labels, turns, bytes, duration, CVE ids proven\nby the payload, path-only CVE candidates and the download URLs the client\nnamed, newest first, with verdict, service and port breakdowns.\n\nUse after ioc_lookup_tool when ","read_only":true}],"server_info":{"name":"HoneyLabs Threat Intelligence","version":"1.2.0"},"category":"security","tags":["web-search","productivity"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-05-20","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/net-honeylabs-mcp/"}