Guard Core vs SecLens.ONE Email Security
Guard Core is an MCP server published by Guard-Core. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). SecLens.ONE Email Security is an MCP server published by seclens.one. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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 |  Guard Core |  SecLens.ONE Email Security |
|---|---|---|
| Official MCP Registry | Listed Version: 1.7.0 Downloads/month (PyPI): 780 Downloads/week (PyPI): 406 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.7.0 Downloads/month (PyPI): 780 Downloads/week (PyPI): 406 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Not listed |
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 | Guard Core | SecLens.ONE Email Security |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | On your machine (guard-core-mcp) | Remote server (seclens.one/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/guard-core/guard-core-mcp | github.com/42sec-pte-ltd/seclens |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-27 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Guard Core
Guard Core security MCP: SecurityConfig validation, docs search, live threat detection.
SecLens.ONE Email Security
Assess any domain's email security across SPF, DMARC, DKIM, MTA-STS, DNSSEC, DANE, and TLS-RPT.
How to run each
Guard Core As a local MCP server: PyPI package
claude mcp add --transport stdio guard-core-mcp -- uvx guard-core-mcpSecLens.ONE Email Security As a remote MCP server
claude mcp add --transport http seclens https://seclens.one/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Guard Core · What it can do: SecLens.ONE Email Security · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.