# SecLens.ONE Email Security (remote · seclens.one)

Assess any domain's email security across SPF, DMARC, DKIM, MTA-STS, DNSSEC, DANE, and TLS-RPT.

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `seclens.one`: 77/100 (this document), [markdown](https://verifymcp.io/servers/one-seclens-seclens/seclens.md), [page](https://verifymcp.io/servers/one-seclens-seclens/seclens)

## Channel facts

- Endpoint: `https://seclens.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 120 tokens (~40/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SecLens.ONE Email Security MCP server?

SecLens.ONE Email Security is a hosted endpoint at https://seclens.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http one-seclens-seclens 'https://seclens.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "one-seclens-seclens": {
      "url": "https://seclens.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "one-seclens-seclens": {
      "type": "http",
      "url": "https://seclens.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.one-seclens-seclens]
url = "https://seclens.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "one-seclens-seclens": {
      "type": "remote",
      "url": "https://seclens.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add one-seclens-seclens --url 'https://seclens.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  one-seclens-seclens:
    url: "https://seclens.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "one-seclens-seclens": {
      "Transport": "http",
      "Url": "https://seclens.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add one-seclens-seclens -t streamable-http -u 'https://seclens.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "one-seclens-seclens": {
      "type": "http",
      "url": "https://seclens.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 72)

First indexed and scored.

## MCP tools (3)

### `assess_domain` (~40 tokens)

Assess Domain Email Security

Start a public SecLens.ONE email-security assessment for a domain. Poll get_result afterwards.

Input parameters:

- `domain` (string, required): Domain name, for example example.com

### `get_result` (~62 tokens)

Get Stored Domain Assessment

Fetch the latest stored public SecLens.ONE assessment for a domain. The JSON includes Remediation.packs, matching the HTML remediation pack. BIMI is included when assessed and does not change the score.

Input parameters:

- `domain` (string, required): Domain name, for example example.com

### `get_summary` (~18 tokens)

Get Global Pulse Corpus Summary

Fetch the live public SecLens.ONE corpus snapshot.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/one-seclens-seclens/seclens#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72

## Common questions

### What is the SecLens.ONE Email Security MCP server?

SecLens.ONE Email Security is an MCP server listed in the public MCP registry as one.seclens/seclens. Assess any domain's email security across SPF, DMARC, DKIM, MTA-STS, DNSSEC, DANE, and TLS-RPT. This page covers its hosted endpoint (https://seclens.one/mcp).

### Is the SecLens.ONE Email Security MCP server safe to use?

SecLens.ONE Email Security scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SecLens.ONE Email Security MCP server expose?

SecLens.ONE Email Security exposes 3 tools: assess_domain, get_result, get_summary. Their descriptions and schemas cost roughly 120 tokens of context every time the server is loaded.

### Does the SecLens.ONE Email Security MCP server require authentication?

No. We connected to SecLens.ONE Email Security without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SecLens.ONE Email Security MCP server still maintained?

SecLens.ONE Email Security is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://seclens.one/mcp
- Repository: https://github.com/42Sec-Pte-Ltd/seclens
- Website: https://seclens.one/
- Changelog RSS feed: https://verifymcp.io/servers/one-seclens-seclens/seclens.xml
- Changelog JSON feed: https://verifymcp.io/servers/one-seclens-seclens/seclens.json
- HTML version of this page: https://verifymcp.io/servers/one-seclens-seclens/seclens