MailAlign
dev.workers.mike-tusa.mailalign/mailalignmailalign.mike-tusa.workers.devstreamable-httpv0.1.2Scanned
Email header analyzer: SPF/DKIM/DMARC/ARC verdicts, domain alignment, hop delays. No lookups.
1 tool: 1 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →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
Only reads 1Show 1 read-only tool
analyze_headersAnalyze pasted raw email headers.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "analyze_headers" says "analyze": a word for reading.
What it can reach
- private-dataThe description's first sentence says "analyze" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "analyze" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Analyze pasted raw email headers. Reports From / Return-Path / Reply-To / DKIM d= alignment (relaxed and strict), SPF / DKIM / DMARC / ARC verdicts as recorded by the receiving servers (Authentication-Results, ARC-*), the Received hop chain oldest first with per-hop delays and public IPs, and plain-English findings with severity and what each means or how to fix it. Makes no network or DNS calls and does not verify signatures. Header text is not stored. Read-only. Same engine as the MailAlign JSON API (POST /api/analyze).
Annotations the server declares
- title: Analyze email headers
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 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.
Looked at Oct 22, 2026, 15:21 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
- 0
- 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
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.
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.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http mailalign https://mailalign.mike-tusa.workers.dev/mcpclaude mcp add --transport http mailalign https://mailalign.mike-tusa.workers.dev/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": [
"mcp__mailalign__analyze_headers"
],
"ask": [],
"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 mailalign. Review it before you use it.
Capability tags behind 1 rule
- mcp__mailalign__analyze_headers private-data, 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://anlyon.dev/api/v1/servers/dev.workers.mike-tusa.mailalign/mailalign/verify?hash=60b87fa1936e03ad7cc89220d7c0e1f5e0559bff52f36fce93b96696ce371bfc" | jq -e '.changed == false'Pinned hash 60b87fa1936e, from Oct 21, 2026, 19:12 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/dev.workers.mike-tusa.mailalign/mailalign/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/dev.workers.mike-tusa.mailalign/mailalign)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.