Developer · Remote MCP server

HoneyLabs

Honeypot probe data: IP reputation, scanners, CVE probing, TLS and SSH fingerprints.

Visit HoneyLabs's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
net.honeylabs/mcp
Version
1.1.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-08-28
Updated
2026-08-28
Publisher
net.honeylabs
Namespace
Namespace verified by the MCP Registry via the domain honeylabs.net · how
Website
honeylabs.net
Repository
github.com/honeylabshq/honeylabs-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.honeylabs.net/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
HoneyLabs Threat Intelligence 1.0.0 · protocol 2025-06-18
Tools discovered
10: search_events_tool, top_attackers_tool, ioc_lookup_tool, cve_lookup_tool, payload_search_tool, attack_timeline_tool, asn_enrich_tool, fingerprint_search_tool, fingerprint_similar_tool, fingerprint_population_tool
Checked on
2026-10-05

How the live check works

How to connect HoneyLabs

HoneyLabs is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.honeylabs.net/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
HonestdogVetted German dog-breeder directory, S-E breed health grades and tests, adoptable shelter dogs.Remote · HTTPLive check: ✓ handshakeserver.honestdog.de
honesty-mcpMCP server exposing 11 honesty-SDK kits (grounding, trust, audit, corroboration) as agent tools.Local · stdionpm: honesty-mcp
HoneycheckBefore buying a token on Arc, test whether it can be sold back. Free, or 1-5c a call over x402.Local · stdionpm: honeycheck-mcp
HoneycombQuery Honeycomb observability data: traces, events, metrics, SLOs, triggers, and boards.Remote · HTTPLive check: sign-in requiredmcp.honeycomb.io
HookdenWebhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures.Remote · HTTPLive check: ✓ handshakehookden.pages.dev
hookline.orgHookline MCP - create webhook endpoints, inspect requests, and validate payloads from AI agents.Local · stdionpm: @hookline/mcp
HooklistenerWebhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay.Remote · HTTPLive check: sign-in requiredapp.hooklistener.com
HookpulseDead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.Remote · HTTPLive check: ✓ handshakehookpulse.net