Domain Trust Check (DNS, Email Auth, TLS, Headers) MCP Server

by pcp183 Your server? Claim it

not responding

Domain Trust Check (DNS, Email Auth, TLS, Headers) is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Check a domain's DNS, SPF/DMARC and TLS before trusting it. $0.003/call via x402.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 23 days of history · worst day 0%

23 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

219 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 October 2026. No other catalogue keeps this.

17 Oct a tool description was rewritten domain_check

17 Oct a tool changed version

Domain Trust Check (DNS, Email Auth, TLS, Headers) does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add domain-check --transport http https://domain-check-production-6228.up.railway.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://domain-check-production-6228.up.railway.app/mcp

~/.codex/config.toml

[mcp_servers.domain-check]
url = "https://domain-check-production-6228.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "domain-check": {
      "url": "https://domain-check-production-6228.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "domain-check": {
      "type": "http",
      "url": "https://domain-check-production-6228.up.railway.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

domain

domain_check

Sanity-check a vendor's or sender's domain before trusting an email, link or payment request. Measured at request time: A/AAAA, NS and MX records, SPF and DMARC policies, DNSSEC (DS), CAA, the TLS certificate on port 443 (issuer, validity, hostname match) and HTTPS security headers, with a list of risk flags. Technical signals only, not a reputation or ownership verdict. Use when an unfamiliar domain appears in an invoice, email or supplier record. $0.003 per call, USDC on Base (x402).

Endpoints

URL	Transport	State	Latency	Checked
https://domain-check-production-6228.up.railway.app/mcp	streamable-http	answering	219 ms	10 min ago

Alternatives to Domain Trust Check (DNS, Email Auth, TLS, Headers)

same job, measured the same way

TamingDNS

by tamingdns

Check SPF, DKIM, DMARC, MX, MTA-STS, TLS-RPT, BIMI, DANE and DNSSEC, and analyse email headers.

10 tools answering

InboxGuards Email Check

by inboxguardstest-api

Check emails before you send, and get a $1 SPF/DKIM/DMARC fix plan for your domain. Pay per call.

4 tools answering

DomainRef - domain and email security check

by domainref

Pay-per-call domain and email security check: SPF, DKIM, DMARC, TLS, DNSSEC, BIMI, with exact fixes.

2 tools answering

DomainCheck

by youraitools

Domain and email trust checks for agents: DNS, SPF/DMARC, disposable email. By Crypto Money Maker

2 tools answering

OrionCMD Checks

by orioncmd-api

Domain threat checks, a 30-day domain watch, TLS/DNS/email-auth checks and a $2 site audit (x402).

14 tools answering

Deliverability Doctor

by integrity-os

Check if a domain can be email-spoofed: SPF, DMARC, DKIM, MX graded from public DNS. Authless.

2 tools answering

DnsGuard

by workers-mike-tusa-dnsguard

Check a domain's email authentication: SPF, DKIM, DMARC, BIMI, MX, MTA-STS, TLS-RPT. Score + fixes.

1 tools answering

Domainposture

by domainposture

Remote MCP server: 19 domain-hygiene and email-auth tools (DNS, SPF, DMARC, DKIM, TLS).

22 tools answering

Domain Trust Check (DNS, Email Auth, TLS, Headers) — questions

Answers built from our own checks of this server.

What can Domain Trust Check (DNS, Email Auth, TLS, Headers) do?

It exposes 1 tools, read directly from the server on our last check. Among them: domain_check. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Domain Trust Check (DNS, Email Auth, TLS, Headers) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 219 ms. The bar chart above shows every period we have measured.

Is Domain Trust Check (DNS, Email Auth, TLS, Headers) still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Domain Trust Check (DNS, Email Auth, TLS, Headers) as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Domain Trust Check (DNS, Email Auth, TLS, Headers)?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Domain Trust Check (DNS, Email Auth, TLS, Headers) need an API key?

No. Domain Trust Check (DNS, Email Auth, TLS, Headers) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.