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

Get the checkout link for a paid daily watch on one domain

spf_watch_subscribe

Read-onlyIdempotent

Operated by an artificial intelligence, not by a person. Return the price, the terms and the checkout link for the paid product this tool covers: a watch on ONE domain. The six reading tools here are free and stay free; this tool exists because a reading answers a question once and a DNS record is a state, not a fact. A watch reads the domain SPF and DMARC on two independent resolvers at least once every 24 hours, emails a first reading as a baseline, then stays silent until something changes: SPF text, counted lookup total, a crossing of 8 or of the RFC 7208 limit of 10, an include added or removed, DMARC p or sp changed, or either record stops resolving. Every alert prints the previous and new reading side by side with the timestamp of each. 12 US dollars per month, one domain. Cancel by one line of email, month in progress refunded. Use this when a caller asks to be told IF a domain record CHANGES, to monitor or watch a domain, or asks what this costs. THIS TOOL DOES NOT TAKE PAYMENT AND DOES NOT START A WATCH: it returns a link a person must open and pay at, and the watch begins only after that payment.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No	Optional. The bare domain the caller is asking about, for example example.com. It is echoed back for convenience; it does not start anything.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cancel`	Yes
`domain`	Yes
`product`	Yes
`operator`	Yes
`details_url`	Yes
`domain_note`	Yes
`operated_by`	Yes
`checkout_url`	Yes
`domains_included`	Yes
`what_is_promised`	Yes
`price_usd_per_month`	Yes
`if_a_reading_is_missed`	Yes
`what_triggers_an_email`	Yes
`the_free_tools_stay_free`	Yes
`this_tool_did_not_do_anything`	Yes

Schema Changelog

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

Changed1 schema field changedSep 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "domain": "example.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": {
+    "cancel": {
+      "properties": {
+        "effect": {
+          "type": "string"
+        },
+        "email": {
+          "type": "string"
+        },
+        "how": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "checkout_url": {
+      "type": "string"
+    },
+    "details_url": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "domain_note": {
+      "type": "string"
+    },
+    "domains_included": {
+      "type": "integer"
+    },
+    "if_a_reading_is_missed": {
+      "type": "string"
+    },
+    "operated_by": {
+      "type": "string"
+    },
+    "operator": {
+      "type": "string"
+    },
+    "price_usd_per_month": {
+      "type": "integer"
+    },
+    "product": {
+      "type": "string"
+    },
+    "the_free_tools_stay_free": {
+      "type": "string"
+    },
+    "this_tool_did_not_do_anything": {
+      "type": "string"
+    },
+    "what_is_promised": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "what_triggers_an_email": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "cancel",
+    "checkout_url",
+    "details_url",
+    "domain",
+    "domain_note",
+    "domains_included",
+    "if_a_reading_is_missed",
+    "operated_by",
+    "operator",
+    "price_usd_per_month",
+    "product",
+    "the_free_tools_stay_free",
+    "this_tool_did_not_do_anything",
+    "what_is_promised",
+    "what_triggers_an_email"
+  ],
+  "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?

The description goes well beyond the annotations by explaining the tool is AI-operated, returns a checkout link rather than starting a watch, requires a person to pay, and begins the watch only after payment. It details the monitoring behavior, alert conditions, baseline email, and pricing, all of which are not visible in annotations.

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 it earns the length by covering purpose, pricing, cancellation, alert behavior, and usage guidance. It is front-loaded with the core purpose and caveats, though the philosophical explanation about DNS records being a state rather than a fact is not strictly necessary.

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?

For a paid subscription-related tool, the description covers price, terms, cancellation, what the watch monitors, alert format, and the crucial limitation that this tool does not start a watch. The optional parameter and absence of required input are fully clarified, and the output schema exists to define the return shape, so nothing essential is missing.

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 optional 'domain' parameter with examples and a clear description. The tool description echoes that the domain is echoed back and does not start anything, which adds no significant semantic meaning beyond the schema. With 100% schema coverage, the baseline 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 states a specific resource ('checkout link for a paid daily watch on ONE domain') and a distinct scope, clearly separating it from the free reading tools. It also explicitly says what the tool does not do, which removes ambiguity about its role.

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 says 'Use this when a caller asks to be told IF a domain record CHANGES, to monitor or watch a domain, or asks what this costs.' It contrasts with the free reading tools and clarifies the tool only returns a link, not a watch, giving clear when-to-use and when-not-to-use guidance.

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?