Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bottled

REMOTE · BOTTLED.EMAIL · SCANNED OCT 13

Branded email on your own domain: send, reply, search, aliases, contacts and campaigns.

Available components

remote · bottled.email 79
0 this week 79 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 102 tokens (~102/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 Management0
  • Stability check failed: schema churn in the 15 days we've observed: 30 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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
Install

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

# add to Claude Code
claude mcp add --transport http email-bottled-bottled 'https://bottled.email/api/mcp/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "email-bottled-bottled": {
      "url": "https://bottled.email/api/mcp/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "email-bottled-bottled": {
      "type": "http",
      "url": "https://bottled.email/api/mcp/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.email-bottled-bottled]
url = "https://bottled.email/api/mcp/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "email-bottled-bottled": {
      "type": "remote",
      "url": "https://bottled.email/api/mcp/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add email-bottled-bottled --url 'https://bottled.email/api/mcp/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  email-bottled-bottled:
    url: "https://bottled.email/api/mcp/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "email-bottled-bottled": {
      "Transport": "http",
      "Url": "https://bottled.email/api/mcp/mcp"
    }
  }
}
# add to Vellum
assistant mcp add email-bottled-bottled -t streamable-http -u 'https://bottled.email/api/mcp/mcp'
// mcp.json
{
  "mcpServers": {
    "email-bottled-bottled": {
      "type": "http",
      "url": "https://bottled.email/api/mcp/mcp"
    }
  }
}

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

Changelog

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.

  • 1 Oct 26 +3
    • 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 +40
    • 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 36

    First indexed and scored.

Diagnostics

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 13 Oct 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 62422 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
MCP tools · 1 exposed · ~102 tokens

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 →

Tool Tokens
check_domain_setup ~102

Check whether a domain is set up to send and receive email: MX records, SPF, DMARC, the detected mail provider, and a graded report with a recommendation. Reads public DNS only. Works with no account and no API key, so use it freely to diagnose a domain before suggesting anyone sign up.

NameTypeReqDescription
domainstringyesDomain 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.

Common questions

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 79 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 102 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 13 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.