Bottled
REMOTE · BOTTLED.EMAIL
Branded email on your own domain: send, reply, search, aliases, contacts and campaigns.
Available components
Last scanned (13 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 → Why this is hard to 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 122 tokens (~122/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- Tool “check_domain_setup” rewrote its description, which is the text the model reads security
- Schema quality: 102 → 122 ▼ functional
- 31 Oct 26 +14
- Stability: fail → pass ▲ security
- 1 Oct 26 0
- Stability: 0.07 → fail ▼ security
- Tool coverage: 62% → 100% ▲ functional
- Schema quality: fail → pass ▲ functional
- Destructive annotations: 0 → pass functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 29 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 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
- 25 Sept 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
- 16 Sept 26 0
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 5 Nov 2026 · Probed https://bottled.email/api/mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bottled.email | CN=YR1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 6227452beef8a003df916068ce1388b0176 |
| SANs: bottled.email | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bottled.email. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| email. | present | 53311 | 8 | Verified |
| bottled.email. | 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 error="invalid_token", error_description="No authorization provided", resource_metadata="https://bottled.email/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://bottled.email/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://sparkbrain.app https://va.vercel-scripts.com https://sellular.online https://sparkads.dev https://www.youtube.com https://s.ytimg.com; style-src 'self' 'unsafe-inline' https://sparkbrain.app https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https:; media-src 'self' https://sparkbrain.app; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Protected resource metadata
| Document | https://bottled.email/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bottled.email/api/mcp/mcp | Verified | 200 | |
| http (plaintext) | http://bottled.email/api/mcp/mcp | HTTPS enforced | 308 | https://bottled.email/api/mcp/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domain_setup ~122
Check whether a domain is set up to send and receive email. Returns its MX records and the mail provider they point at, its SPF record, its DMARC policy, a score out of 100 with a letter grade, the individual findings behind that score, and the next technical step. Reads public DNS only: no mail is sent, no mailbox is accessed, and no account or API key is required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. example.com. A full URL or an email address is accepted and reduced to its hostname. |
No output schema declared.
No examples provided.
How do I install the Bottled MCP server?
Bottled is a hosted endpoint at https://bottled.email/api/mcp/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.
remote · bottled.email
claude mcp add --transport http email-bottled-bottled 'https://bottled.email/api/mcp/mcp'
What is the Bottled MCP server?
Bottled is an MCP server listed in the public MCP registry as email.bottled/bottled. Branded email on your own domain: send, reply, search, aliases, contacts and campaigns. This page covers its hosted endpoint (https://bottled.email/api/mcp/mcp).
Is the Bottled MCP server safe to use?
Bottled scores 93 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 Bottled MCP server expose?
Bottled exposes 1 tool: check_domain_setup. Their descriptions and schemas cost roughly 122 tokens of context every time the server is loaded.
Does the Bottled MCP server require authentication?
Yes. Bottled asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Bottled MCP server still maintained?
Bottled 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.