io.github.lazymac2x/domain-intel vs Securitytrails
io.github.lazymac2x/domain-intel is an MCP server published by lazymac2x. Marketplaces we read that list it: 1 (Official MCP Registry). Securitytrails is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.lazymac2x/domain-intel | Securitytrails |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | Remote server (api.lazy-mac.com/domain-intel/mcp) | Remote server (gateway.pipeworx.io/securitytrails/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/lazymac2x/domain-intel-api | github.com/pipeworx-io/mcp-securitytrails |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check | Responded 5 days ago | Responded 5 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.lazymac2x/domain-intel
Cloudflare Workers MCP server: domain-intel
Securitytrails
SecurityTrails MCP — wraps SecurityTrails API (securitytrails.com)
How to run each
io.github.lazymac2x/domain-intel As a remote MCP server
claude mcp add --transport http domain-intel https://api.lazy-mac.com/domain-intel/mcp
Securitytrails As a remote MCP server
claude mcp add --transport http securitytrails https://gateway.pipeworx.io/securitytrails/mcp
Requires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.lazymac2x/domain-intel publish no settings it asks for, so we do not compare settings.
What it can do: io.github.lazymac2x/domain-intel · What it can do: Securitytrails · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.