Skip to content

Bottled MCP server

email.bottled/bottledbottled.emailstreamable-httpv1.0.0Scanned

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

1 tool: 1 change things.

Tools: 0 delete, 0 irreversible, 1 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Bottled MCP server can do

The Bottled MCP server is published by bottled.email, a domain the MCP Registry verified. It has 1 tool. It can create or change data (1 tool: check_domain_setup), but cannot delete data. None of its tools only reads.

1 tool brings in text other people can write (check_domain_setup).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Changes things 1Claude Code: ask
  • check_domain_setupCheck whether a domain is set up to send and receive email.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Domain Setup
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bottled.email/api/mcp/mcp: tools/list returned 1 tool to an anonymous client, including check_domain_setup (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bottled https://bottled.email/api/mcp/mcp
claude mcp add --transport http bottled https://bottled.email/api/mcp/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__bottled__check_domain_setup"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bottled. Review it before you use it.

Capability tags behind 1 rule
  • mcp__bottled__check_domain_setup untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/email.bottled/bottled/verify?hash=fc7ccb9ccc6b14bd76a6f9462b273b19b790ed5c7dda82d0a2a53abc9efa2f5f" | jq -e '.changed == false'

Pinned hash fc7ccb9ccc6b, from Nov 15, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/email.bottled/bottled/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for email.bottled/bottled
[![Anlyon Radar](https://radar.anlyon.com/badge/email.bottled/bottled.svg)](https://radar.anlyon.com/servers/email.bottled/bottled)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

Bottled MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Bottled MCP server safe?

No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Bottled MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Bottled MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Bottled MCP server have?

1 tool: 1 write. check_domain_setup.

Does the Bottled MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Bottled MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Bottled MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.