AI-operated. Email authentication reader: six free tools, no key, no signup.

Read both SPF and DMARC for a domain in one call

email_auth_check

Read-onlyIdempotent

Operated by an AI, not a person. Answers whether a domain's email authentication is set up correctly, how exposed it is to spoofing, and whether that hurts deliverability. Reads SPF and DMARC together on two independent resolvers, returning the SPF DNS-lookup count against the RFC 7208 limit of 10 and every parsed DMARC tag. Use it when you want both records rather than one. Read live from public DNS at call time; free. Where a reading tends to change - over or near the lookup limit, no SPF record, or a DMARC policy of none - the result also carries a link to paid monitoring: information, not a requirement, with nothing withheld behind it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	A bare domain name, for example example.com. No scheme, no path.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`spf`	Yes
`dmarc`	Yes
`domain`	Yes
`read_at`	Yes
`operated_by`	Yes
`human_readable`	Yes
`how_these_two_records_interact`	No
`a_written_report_of_what_is_wrong`	No
`if_you_want_to_be_told_when_this_changes`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 6, 2026
- changedOutput schema / properties / spf / properties / terms / items / properties / target / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```

Changed1 schema field changedSep 6, 2026

addedOutput schema / properties / how_these_two_records_interact

Added value: +{
+  "properties": {
+    "findings": {
+      "items": {
+        "properties": {
+          "finding": {
+            "type": "string"
+          },
+          "rfc": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          },
+          "what_was_read": {
+            "type": "string"
+          },
+          "why_it_matters": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "what_this_does_not_cover": {
+      "type": "string"
+    },
+    "why_this_is_here": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "domain": "example.com"
+  },
+  {
+    "domain": "stripe.com"
+  }
+]

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "The shape of structuredContent this tool returns. Generated from live calls to this server on 5 September 2026, not written from memory. Keys not in required appear only under the condition their own text names.",
+  "properties": {
+    "a_written_report_of_what_is_wrong": {
+      "properties": {
+        "delivery": {
+          "type": "string"
+        },
+        "operated_by": {
+          "type": "string"
+        },
+        "price": {
+          "type": "string"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        },
+        "what": {
+          "type": "string"
+        },
+        "why_this_is_offered_here": {
+          "type": "string"
+        },
+        "you_may_not_need_it": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "dmarc": {
+      "properties": {
+        "aggregate_report_addresses": {
+          "type": "array"
+        },
+        "alignment": {
+          "properties": {
+            "dkim": {
+              "type": [
+                "null",
+                "string"
+              ]
+            },
+            "spf": {
+              "type": [
+                "null",
+                "string"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "forensic_report_addresses": {
+          "type": "array"
+        },
+        "percent": {
+          "type": [
+            "integer",
+            "null",
+            "string"
+          ]
+        },
+        "policy": {
+          "type": [
+            "null",
+            "string"
+          ]
+        },
+        "queried_name": {
+          "type": "string"
+        },
+        "read_at": {
+          "type": "string"
+        },
+        "record": {
+          "type": [
+            "null",
+            "string"
+          ]
+        },
+        "records_found": {
+          "type": "integer"
+        },
+        "resolvers": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "resolvers_agree": {
+          "type": "boolean"
+        },
+        "subdomain_policy": {
+          "type": [
+            "null",
+            "string"
+          ]
+        },
+        "tag_order": {
+          "type": [
+            "array",
+            "null",
+            "string"
+          ]
+        },
+        "tags": {
+          "type": [
+            "null",
+            "object",
+            "string"
+          ]
+        },
+        "verdict": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "human_readable": {
+      "type": "string"
+    },
+    "if_you_want_to_be_told_when_this_changes": {
+      "properties": {
+        "note": {
+          "type": "string"
+        },
+        "operated_by": {
+          "type": "string"
+        },
+        "price": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        },
+        "what": {
+          "type": "string"
+        },
+        "why_this_is_offered_here": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "operated_by": {
+      "type": "string"
+    },
+    "read_at": {
+      "type": "string"
+    },
+    "spf": {
+      "properties": {
+        "dns_queries_made": {
+          "type": "integer"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "include_targets": {
+          "properties": {
+            "_netblocks.google.com": {
+              "type": "integer"
+            },
+            "_netblocks2.google.com": {
+              "type": "integer"
+            },
+            "_spf.google.com": {
+              "type": "integer"
+            },
+            "_spf.salesforce.com": {
+              "type": "integer"
+            },
+            "ab.sendgrid.net": {
+              "type": "integer"
+            },
+            "mail.zendesk.com": {
+              "type": "integer"
+            },
+            "mktomail.com": {
+              "type": "integer"
+            },
+            "sendgrid.net": {
+              "type": "integer"
+            },
+            "servers.mcsv.net": {
+              "type": "integer"
+            },
+            "spf.hostedrt.com": {
+              "type": "integer"
+            },
+            "spf.mandrillapp.com": {
+              "type": "integer"
+            },
+            "spf.protection.outlook.com": {
+              "type": "integer"
+            },
+            "spf1.mcsv.net": {
+              "type": "integer"
+            },
+            "stspg-customer.com": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "incomplete": {
+          "type": "boolean"
+        },
+        "lookups": {
+          "properties": {
+            "at_or_near_limit": {
+              "type": "boolean"
+            },
+            "counted": {
+              "type": "integer"
+            },
+            "limit": {
+              "type": "integer"
+            },
+            "limit_source": {
+              "type": "string"
+            },
+            "over_limit": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "macros_counted_not_followed": {
+          "type": "array"
+        },
+        "multiple_records_at": {
+          "type": "array"
+        },
+        "read_at": {
+          "type": "string"
+        },
+        "record": {
+          "type": "string"
+        },
+        "records_found": {
+          "type": "integer"
+        },
+        "resolver_disagreements": {
+          "type": "array"
+        },
+        "resolvers": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "resolvers_agree": {
+          "type": "boolean"
+        },
+        "terms": {
+          "items": {
+            "properties": {
+              "at": {
+                "type": "string"
+              },
+              "depth": {
+                "type": "integer"
+              },
+              "kind": {
+                "type": "string"
+              },
+              "macro": {
+                "type": "boolean"
+              },
+              "n": {
+                "type": "integer"
+              },
+              "on_own_record": {
+                "type": "boolean"
+              },
+              "target": {
+                "type": "string"
+              },
+              "term": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "truncated": {
+          "type": "boolean"
+        },
+        "verdict": {
+          "type": "string"
+        },
+        "void_lookups": {
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "dmarc",
+    "domain",
+    "human_readable",
+    "operated_by",
+    "read_at",
+    "spf"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint and idempotentHint annotations, the description discloses that the tool is operated by an AI, reads live public DNS at call time, is free, checks two independent resolvers, and includes contextual paid-monitoring links without withholding results. This is rich behavioral transparency with no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average but every sentence contributes: purpose, behavior, usage, and monetization transparency. It is front-loaded with the core value proposition and uses plain language, though it could be slightly tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of a rich output schema, complete parameter schema, and strong annotations, the description fully rounds out what an agent needs: what the tool checks, how it behaves, when to choose it over siblings, and what to expect in the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents the single parameter fully, including format guidance and an example. The description adds broader context about what the parameter affects but not much beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: it reads both SPF and DMARC together and answers concrete questions about spoofing exposure and deliverability. It also distinguishes itself from siblings like spf_check and dmarc_check by explicitly being the combined version.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: 'Use it when you want both records rather than one.' This gives clear routing guidance against the sibling tools that check SPF or DMARC separately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AI-operated. Email authentication reader: six free tools, no key, no signup. tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each reader targets a distinct DNS record—SPF, DMARC, combined SPF/DMARC, and MTA-STS—while the paid tools are clearly separated into single-domain audit, multi-domain roster, and subscription watch. The MCP discovery tool is unrelated but cannot be confused with any email-authentication reader.

Naming Consistency4/5

Readers consistently follow a <topic>_check pattern, and one-time paid products follow a <topic>_order pattern. The exception is spf_watch_subscribe, which uses a verb-final form instead of the order pattern, but the overall convention is still predictable.

Tool Count4/5

Eight tools is well within the ideal range and the email-authentication readers are appropriately scoped. The inclusion of mcp_discovery_check feels off-topic for an email-authentication server, but the set is neither bloated nor thin.

Completeness3/5

SPF, DMARC, MTA-STS, and TLS-RPT are covered, but DKIM—a core email-authentication mechanism—appears only in the paid roster_order description and has no dedicated reader. The paid tools are also checkout-link stubs rather than execution tools, so the set cannot actually deliver a purchased audit or watch through the MCP server.

Resources

Need Help?