Skip to content
Quiet Failures logo

Quiet Failures MCP server

Which MCP servers are Quiet Failures's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to Quiet Failures

Whose server it is
  • Registry namecom.quietfailures/quiet-failuresverified in the MCP registry

The registry name sits under quietfailures.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools6
  • Server calls itselfquiet-failures
  • Server version1.4.10
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 679 ms.

Should an agent connect itConnect it
  • Its tools do every use case we checked: check SPF, DKIM and DMARC email authentication settings; scan for dangling DNS records pointing at unowned services.

Once connected

  • For "check SPF, DKIM and DMARC email authentication settings", the likely first call is check_email_auth.
  • For "scan for dangling DNS records pointing at unowned services", the likely first call is check_subdomain_takeover.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 10, the first on 2026-10-25
  • INITE MCP score100 of 100answers 100 · does the job 100 · definitions 100 · context 100 · connects 100
  • What an agent can do with it2 of 2 use cases
  • Answered100% of days10 of 10 daily checks
  • Median first answer596 ms
  • Space in an agent's context≈ 808 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · check SPF, DKIM and DMARC email authentication settings
  • can do · scan for dangling DNS records pointing at unowned services
  • not sure · verify registrar lock and domain expiry dates across domains

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-25
  • list_base_rates

    Catalog of all published Quiet Failures base rates: metric id, the global question, the current global figure, sample size, severity, and every published segment slug (valid `segment` values for get_base_rate). Use get_base_rate for full…

  • find_base_rate

    Search the Quiet Failures base rates by keyword (e.g. "dmarc", "certificate expiry uk", "subdomain takeover"). Returns matching metrics and their most citable segments.

  • get_base_rate

    Full detail for one Quiet Failures base rate segment: the figure with confidence interval, how it is measured, why it matters, the limits of the measurement, the recent time series, and the canonical source URL to cite. Segment defaults…

  • check_email_auth

    Live SPF, DKIM and DMARC audit of up to 50 domains the user owns or asks about. Returns a per-domain breakdown plus a portfolio grade. Compare against the base rates: most of the web fails these controls. Rate-limited per client.

  • check_subdomain_takeover

    Live scan of one domain: enumerate its subdomains (CT logs + DNS), then test each for dangling references on 13 cloud providers. Slow on large domains (up to a few minutes). Rate-limited per client.

  • check_whois

    Live WHOIS lookup for up to 100 domains: expiry date, registrar, nameservers. Use to catch registrations about to lapse. Rate-limited per client.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "quiet-failures": {
      "type": "http",
      "url": "https://mcp.quietfailures.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http quietfailures https://mcp.quietfailures.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.quietfailures.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.