EmailMCP
REMOTE · MCP.SETIP.IO · SCANNED AUG 3
AI agent email — 23 tools free to read inbox, 28 paid to send. $9.99/mo. Token auto-provisioned.
Available components
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. How we score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3724 tokens (~66/item across 56 items; 56 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.setip.io
claude mcp add --transport http io-setip-emailmcp https://mcp.setip.io/mcp
[mcp_servers.io-setip-emailmcp] url = "https://mcp.setip.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-setip-emailmcp": {
"type": "remote",
"url": "https://mcp.setip.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-setip-emailmcp --url https://mcp.setip.io/mcp --transport streamable-http
mcp_servers:
io-setip-emailmcp:
url: "https://mcp.setip.io/mcp" {
"mcpServers": {
"io-setip-emailmcp": {
"type": "http",
"url": "https://mcp.setip.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.setip.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=setip.io | CN=YR1,O=Let's Encrypt,C=US | 9 Jul 2026 | 7 Oct 2026 | RSA 2048 | SHA256-RSA | 5db34c4ac6c2e9adc995d07ffbfdfc4c304 |
| SANs: *.setip.io, setip.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.setip.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| setip.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="EmailMCP MCP", error="invalid_token", error_description="Set EMAILMCP_MCP_TOKEN and configure Codex with --bearer-token-env-var EMAILMCP_MCP_TOKEN"
Bearer realm="EmailMCP MCP", error="invalid_token", error_description="Set EMAILMCP_MCP_TOKEN and configure Codex with --bearer-token-env-var EMAILMCP_MCP_TOKEN"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline';style-src 'self' 'unsafe-inline';img-src 'self' data: https:;base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';object-src 'none';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.setip.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.setip.io/mcp | HTTPS enforced | 301 | https://mcp.setip.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
stop_smtp_receiver ~17
Stop the SMTP forward receiver server
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
test_email_config ~40
Test email configuration by sending a test email
| Name | Type | Req | Description |
|---|---|---|---|
| test_email | string | — | Email address to send test email to (optional, defaults to from_email) |
No output schema declared.
No examples provided.
update_email_rule ~87
Update an existing email rule (enable/disable, change match/actions/priority)
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | — | New actions |
| enabled | boolean | — | Enable or disable the rule |
| match | object | — | New match conditions |
| priority | number | — | New priority |
| rule_id | string | yes | Rule ID to update |
| stop | boolean | — | Stop after match |
No output schema declared.
No examples provided.
validate_email ~55
Validate email addresses and check deliverability
| Name | Type | Req | Description |
|---|---|---|---|
| check_mx | boolean | — | Check MX records for domain |
| check_smtp | boolean | — | Perform SMTP validation |
| emails | array | yes | Array of email addresses to validate |
No output schema declared.
No examples provided.
verify_autonomous_setup ~41
Verify that autonomous email is properly configured: DNS records, DKIM, SMTP send/receive
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Your email domain to verify |
No output schema declared.
No examples provided.
verify_email_setup ~86
Verify IP whitelisting and email provider configuration
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | — | Domain to check for DNS records (required if include_dns is true) |
| include_dns | boolean | — | Include DNS record verification |
| provider | string | yes | Email provider to verify, or "all" for all configured providers |
| test_email | string | — | Optional test email address to verify delivery |
No output schema declared.
No examples provided.