Bottled

email.bottledPublished by bottled.emailOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Bottled is a remote MCP server for branded email on your own domain; its listed tool checks a domain's mail DNS setup and grades it.

What you can do
Check a domain's email readiness: MX records, SPF, DMARC, the detected mail provider and a graded report with a recommendation. Runs on public DNS only, so it can be used without an account or API key. The registry description also presents the service as branded email on your own domain, covering sending, replies, search, aliases, contacts and campaigns, but only the domain-check tool is listed here.
When to use it
Useful when you want to diagnose whether a domain is correctly configured to send and receive email before setting up branded mail, or to sanity-check MX, SPF and DMARC records and get a plain recommendation.
Requirements
A remote endpoint reached over streamable HTTP; no local runtime, account or API key is needed for the listed domain-check tool. Network access to the endpoint and public DNS lookups are required.
Before you install
The listed tool only reads public DNS, so it changes nothing. The broader branded-email service described in the registry would involve sending mail and managing contacts and campaigns, which are actions to review before relying on it; this listing shows no tools for those.

Installation

In SourceWeft

  1. Open Bottled in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/email.bottled%2Fbottled/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bottled": {
      "type": "http",
      "url": "https://bottled.email/api/mcp/mcp"
    }
  }
}

Tools

1

check_domain_setup

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.

Parametersdomainrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.