Did They Open MCP server
com.didtheyopen/mcpdidtheyopen.comstreamable-httpv0.1.0Scanned
Open tracking for the email your agent already sends from your Gmail or Outlook.
5 tools: 5 change things.
- Reads private data · 1
- Reads text others write · 5
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Did They Open MCP server can do
The Did They Open MCP server is published by didtheyopen.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: didtheyopen_signup, didtheyopen_track_email, didtheyopen_check_email, didtheyopen_new_opens and 1 more), but cannot delete data. None of its tools only reads.
1 tool reads private data (didtheyopen_track_email); 5 tools bring in text other people can write (didtheyopen_signup, didtheyopen_track_email, didtheyopen_check_email and 2 more).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.1.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.
5 tools
Changes things 5Claude Code: ask
didtheyopen_accountPlan, trial emails left, whether new emails can be tracked, today usage, and upgrade links.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 Plan, trial emails left, whether new emails can be tracked, today usage, and upgrade links.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
didtheyopen_check_emailOpens so far for one tracked email: count, last time, and each open with device family.Reads text others write1 finding
Why it is in this group
- The description's first verb is "open": a word for a change.
- 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.
Findings
- Warn
The server marks "didtheyopen_check_email" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "open": a word for a change.
Description, as the server wrote it Opens so far for one tracked email: count, last time, and each open with device family.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
didtheyopen_new_opensWhat changed since a cursor, summarised per email, each open exactly once.Reads text others write1 finding
Why it is in this group
- The name "didtheyopen_new_opens" says "open": a word for a change.
- 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.
Findings
- Warn
The server marks "didtheyopen_new_opens" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "didtheyopen_new_opens" says "open": a word for a change.
Description, as the server wrote it What changed since a cursor, summarised per email, each open exactly once. Meant to run without the owner asking, as one permanent recurring job every 10 to 15 minutes: it says which emails are worth telling the owner about right now (first open, a new device, a return after a pause) and which are noise. First call (or after losing the cursor): since = an ISO time such as when tracking started or just before your last check. Then pass back the returned cursor and keep it in durable notes.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
didtheyopen_signupCreate a didtheyopen account (no email needed).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "create": a word for a change.
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 Create a didtheyopen account (no email needed). Use only when no agent key is set for this server (Authorization header). Returns an agent key for this server and a dashboard login for the owner, shown once.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
didtheyopen_track_emailGet a tracking pixel for ONE email the owner asked to track.Reads private dataReads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe name "didtheyopen_track_email" says "email": it reads mail.
- private-dataThe description's first sentence says "get" and "email": it reads mail.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "didtheyopen_track_email" says "email": it reads inbound email, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
Findings
- Warn
The server marks "didtheyopen_track_email" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "get": a word for reading.
Description, as the server wrote it Get a tracking pixel for ONE email the owner asked to track. Returns an <img> tag to put at the end of the HTML body before sending, and, given the links of the email (pass them by default), a tracked address for each link. Never use for plain-text emails or sensitive correspondence. After sending, keep watching with didtheyopen_new_opens on a schedule and tell the owner when it is opened, without waiting to be asked.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- 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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- 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.
Looked at Nov 20, 2026, 18:18 UTC, unchanged since Nov 20, 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
- 5
- 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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://p.didtheyopen.com/mcp: tools/list returned 5 tools to an anonymous client, including didtheyopen_signup (write), didtheyopen_track_email (write), didtheyopen_check_email (write), didtheyopen_new_opens (write), didtheyopen_account (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "didtheyopen_track_email" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "get": a word for reading.
The server marks "didtheyopen_check_email" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "open": a word for a change.
The server marks "didtheyopen_new_opens" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "didtheyopen_new_opens" says "open": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http didtheyopen https://p.didtheyopen.com/mcpclaude mcp add --transport http didtheyopen https://p.didtheyopen.com/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__didtheyopen__didtheyopen_signup",
"mcp__didtheyopen__didtheyopen_track_email",
"mcp__didtheyopen__didtheyopen_check_email",
"mcp__didtheyopen__didtheyopen_new_opens",
"mcp__didtheyopen__didtheyopen_account"
],
"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 didtheyopen. Review it before you use it.
Capability tags behind 5 rules
- mcp__didtheyopen__didtheyopen_signup untrusted-input
- mcp__didtheyopen__didtheyopen_track_email private-data, untrusted-input
- mcp__didtheyopen__didtheyopen_check_email untrusted-input
- mcp__didtheyopen__didtheyopen_new_opens untrusted-input
- mcp__didtheyopen__didtheyopen_account 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/com.didtheyopen/mcp/verify?hash=2c654cfdf9521ce29491cd7093ed3254a14d2dc211ebe29d050b43b8c9aafd74" | jq -e '.changed == false'Pinned hash 2c654cfdf952, from Nov 20, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.didtheyopen/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.didtheyopen/mcp)Source: MCP Registry. Synced Nov 20, 2026, 10:17 UTC.
Did They Open MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Did They Open MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 3 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 Did They Open MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Did They Open 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 Did They Open MCP server have?
- 5 tools: 5 write. didtheyopen_signup, didtheyopen_track_email, didtheyopen_check_email, didtheyopen_new_opens and didtheyopen_account.
Does the Did They Open MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Did They Open MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Did They Open MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.