What is the key difference between Honeylabs MCP and Kastell?

Honeylabs MCP belongs to the Security category with cloud HTTP/SSE execution, while Kastell belongs to the Security category with local stdio execution.

How do I install Honeylabs MCP or Kastell in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Honeylabs MCP and Kastell free or paid?

Honeylabs MCP operates under a Freemium model (API Key required). Kastell operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Honeylabs MCP lists 8 tools with 4 views and 2 GitHub stars. Kastell lists 6 tools with 4 views and 59 GitHub stars.

Can I use both Honeylabs MCP and Kastell together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Honeylabs MCP vs Kastell

In-depth architectural comparison of the Honeylabs MCP and Kastell MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Honeylabs MCP

Security · Remote HTTP/SSE

Quality: 59/100 (Good) | Auth: API Key required

Kastell

Security · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Verdict Summary: Choose Honeylabs MCP if you need specialized Security tools running via a hosted cloud SSE transport. Choose Kastell if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Honeylabs MCP when:

You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Freemium).
Primary tools included: ioc_lookup, top_attackers, search_events.

Explore Honeylabs MCP Details

Choose Kastell when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Server security audits with remediation, SSH hardening and fail2ban setup, UFW firewall management.

Explore Kastell Details

Feature & Specification Comparison

Specification	Honeylabs MCP honeylabshq Security	Kastell kastelldev Security
Summary	Honeypot threat intelligence for AI agents: 90 days of probe data from a sensor network for IP reputation, scanner classification, CVE probing trends, and JA4/JA4H/HASSH fingerprints. Remote MCP, free tier.	Server security auditing and hardening toolkit. 413 security checks across 29 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 19-step production hardening, fleet management, and forensic evidence collection. Supports Hetzner, DigitalOcean, Vultr, and Linode. 13 MCP tools.
Category & Scope

Tools & Capabilities Breakdown

Honeylabs MCP Tools (8)

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.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Honeylabs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "honeylabshq-honeylabs-mcp": {
      "url": "https://mcp.honeylabs.net/mcp"
    }
  }
}

Kastell Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kastelldev-kastell": {
      "command": "npx",
      "args": [
        "-y",
        "kastell"
      ]
    }
  }
}

Frequently Asked Questions

Honeylabs MCP is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Kastell belongs to Security using local stdio subprocess. Select Honeylabs MCP when you need capabilities focused on security and Kastell when you require tools for security.

More alternatives to Honeylabs MCP More alternatives to Kastell Security category hub