Skip to content

OutboundAuth Deliverability MCP server

io.github.SaqibNaseer404/outboundauthSaqibNaseer404streamable-httpv1.2.0Scanned

Free SPF, DKIM, DMARC, blacklist, MX and bounce checks for any domain, as MCP tools for AI agents.

9 tools: 7 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

7 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.
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 OutboundAuth Deliverability MCP server can do

The OutboundAuth Deliverability MCP server is published by the GitHub account SaqibNaseer404. It has 9 tools. It can create or change data (7 tools: check_spf, check_dmarc, check_dkim, check_email_auth and 3 more), but cannot delete data. 2 tools only read.

2 tools read private data (analyze_bounce and analyze_email_headers); 9 tools bring in text other people can write (check_spf, check_dmarc, check_dkim and 6 more).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

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

Last scanned Nov 20, 2026, version 1.2.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.

9 tools

Changes things 7Claude Code: ask
  • analyze_bounceExplain an email bounce in plain English: paste the full bounce message or just the error (e.g.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "analyze_bounce" says "analyze": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "explain" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "explain" and "email": it reads inbound email, which other people can write.

    Findings

    • Warn

      The server marks "analyze_bounce" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "analyze_bounce" says "analyze": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Explain an email bounce in plain English: paste the full bounce message or just the error (e.g. "550 5.7.1"). Returns whether it is a hard or soft bounce, what happened, the likely cause (list quality, reputation, policy, authentication, temporary), and the fix.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_blacklistsCheck a domain's sending IPs (resolved from its mail servers) and/or a specific IP against 7 major DNS blacklists (Spamhaus ZEN, SpamCop, PSBL, UCEPROTECT, Mailspike, DroneBL, UBL)…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 a domain's sending IPs (resolved from its mail servers) and/or a specific IP against 7 major DNS blacklists (Spamhaus ZEN, SpamCop, PSBL, UCEPROTECT, Mailspike, DroneBL, UBL). Reports listed or clean per list, per IP.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_dkimLook up the live DKIM TXT record for a selector (<selector>._domainkey.<domain>) and evaluate the key: version, key type, public key presence.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
    Look up the live DKIM TXT record for a selector (<selector>._domainkey.<domain>) and evaluate the key: version, key type, public key presence. Follows CNAMEs (e.g. Microsoft 365 / Google selectors).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_dmarcLook up the live DMARC TXT record at _dmarc.<domain> and evaluate it: policy (none/quarantine/reject), aggregate reporting (rua).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
    Look up the live DMARC TXT record at _dmarc.<domain> and evaluate it: policy (none/quarantine/reject), aggregate reporting (rua). Returns a scored verdict with findings.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_email_authRun the complete deliverability authentication check for a domain: SPF, DMARC, DKIM (probes common selectors), and MX records.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "run": 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 "check_email_auth" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run the complete deliverability authentication check for a domain: SPF, DMARC, DKIM (probes common selectors), and MX records. Returns a scored verdict per area plus an overall summary.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_mx_healthLook up a domain's MX records and evaluate them: priorities, whether each mail server resolves, the likely mail provider (Google Workspace, Microsoft 365, …), and obvious misconfig…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
    Look up a domain's MX records and evaluate them: priorities, whether each mail server resolves, the likely mail provider (Google Workspace, Microsoft 365, …), and obvious misconfigurations. Returns a scored verdict with findings.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_spfLook up the live SPF TXT record for a domain and evaluate it: version tag, default policy (-all vs ~all), the 10-DNS-lookup limit, PTR use.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
    Look up the live SPF TXT record for a domain and evaluate it: version tag, default policy (-all vs ~all), the 10-DNS-lookup limit, PTR use. Returns a scored verdict with findings.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • analyze_email_headersExplain raw email headers in plain English: the Authentication-Results verdicts for SPF, DKIM and DMARC (with the domains each check covered), From vs Return-Path alignment, and th…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "analyze_email_headers" says "analyze": a word for reading.

    What it can reach

    • private-dataThe name "analyze_email_headers" says "analyze" and "email": it reads mail.
    • private-dataThe description's first sentence says "explain" and "email": it reads mail.
    • untrusted-inputThe name "analyze_email_headers" says "analyze" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "explain" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Explain raw email headers in plain English: the Authentication-Results verdicts for SPF, DKIM and DMARC (with the domains each check covered), From vs Return-Path alignment, and the Received hop count. Paste the full headers ("Show original" in Gmail).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_domain_healthOne combined health report for a domain: SPF, DKIM (common selectors), DMARC, MX and blacklist status, with an overall score out of 100, the top problems, and the recommended fix o…Reads text others writeNo findings

    Why it is in this group

    • The name "get_domain_health" says "get": a word for reading.

    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
    One combined health report for a domain: SPF, DKIM (common selectors), DMARC, MX and blacklist status, with an overall score out of 100, the top problems, and the recommended fix order.

    Annotations the server declares

    • 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 outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write9
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:19 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
7
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 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://outboundauth.com/mcp: tools/list returned 10 tools to an anonymous client, including check_spf (write), check_dmarc (write), check_dkim (write), check_email_auth (write), analyze_bounce (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "check_email_auth" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "analyze_bounce" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "analyze_bounce" says "analyze": a word for reading.

    What this check looks for

History

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

  1. Tools5 added.+5 addedView diff

Install

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

claude mcp add --transport http outboundauth https://outboundauth.com/mcp
claude mcp add --transport http outboundauth https://outboundauth.com/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": [
      "mcp__outboundauth__analyze_email_headers",
      "mcp__outboundauth__get_domain_health"
    ],
    "ask": [
      "mcp__outboundauth__check_spf",
      "mcp__outboundauth__check_dmarc",
      "mcp__outboundauth__check_dkim",
      "mcp__outboundauth__check_email_auth",
      "mcp__outboundauth__analyze_bounce",
      "mcp__outboundauth__check_blacklists",
      "mcp__outboundauth__check_mx_health"
    ],
    "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 outboundauth. Review it before you use it.

Capability tags behind 9 rules
  • mcp__outboundauth__check_spf untrusted-input
  • mcp__outboundauth__check_dmarc untrusted-input
  • mcp__outboundauth__check_dkim untrusted-input
  • mcp__outboundauth__check_email_auth untrusted-input
  • mcp__outboundauth__analyze_bounce private-data, untrusted-input
  • mcp__outboundauth__check_blacklists untrusted-input
  • mcp__outboundauth__check_mx_health untrusted-input
  • mcp__outboundauth__analyze_email_headers private-data, untrusted-input
  • mcp__outboundauth__get_domain_health 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/io.github.SaqibNaseer404/outboundauth/verify?hash=e87ac3ae6847f3555094dab2ec448c96a6d8509eca3fb3135713b7caa65c8644" | jq -e '.changed == false'

Pinned hash e87ac3ae6847, 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/io.github.SaqibNaseer404/outboundauth/changes.xml

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

Badge

Anlyon Radar badge for io.github.SaqibNaseer404/outboundauth
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.SaqibNaseer404/outboundauth.svg)](https://radar.anlyon.com/servers/io.github.SaqibNaseer404/outboundauth)

Source: MCP Registry · repository. Synced Nov 20, 2026, 11:17 UTC.

OutboundAuth Deliverability MCP server: questions and answers

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

Is the OutboundAuth Deliverability MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 7 of which can change, send or delete something, and 2 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 OutboundAuth Deliverability MCP server delete data?

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

Can the OutboundAuth Deliverability 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 OutboundAuth Deliverability MCP server have?

9 tools: 7 write, 2 read. check_spf, check_dmarc, check_dkim, check_email_auth, analyze_bounce, check_blacklists, check_mx_health, analyze_email_headers and 1 more.

Does the OutboundAuth Deliverability MCP server need sign-in or OAuth?

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

Does the OutboundAuth Deliverability MCP server send data to outside services?

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

Has the OutboundAuth Deliverability MCP server changed its tools?

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