Honeylabs MCP vs Shohei

In-depth architectural comparison of the Honeylabs MCP and Shohei 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.

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 Shohei 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: DNS, DNSSEC, DoH, DoT, and DoQ diagnostics, TLS certificate and DANE/TLSA inspection, SPF, DKIM, DMARC, BIMI, and MTA-STS checks.

Explore Shohei Details

Feature & Specification Comparison

Specification	Honeylabs MCP honeylabshq Security	Shohei kent-tokyo 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.	Rust infrastructure diagnostics MCP server for AI agents: DNS checks, TLS certificate chain inspection, email security, global DNS propagation, and DNS latency benchmarking.
Category & Scope

Tools & Capabilities Breakdown

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).

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

{
  "mcpServers": {
    "kent-tokyo-shohei": {
      "command": "npx",
      "args": [
        "-y",
        "kent-tokyo-shohei"
      ]
    }
  }
}

Related MCP Server Comparisons