Mmcp.market

Quiet Failures MCP server

by quietfailures.com·com.quietfailures/quiet-failures·v1.4.8

Open weekly security base rates (CC BY 4.0), plus live DMARC, takeover and WHOIS checks.

C56/100grade C
What users say
No reviews yet
Be the first
Safety scan
C56/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Quiet Failures yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Quiet Failures tools (6, 1 write)

write = sends, deletes, buys or posts
  • check_email_authwrite actionFree

    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_takeoverFree

    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_whoisFree

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

  • find_base_rateFree

    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_rateFree

    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 to "global"; country slugs (gb, fr, us…) and company cuts (gb-companies, gb-small…) are also published.

  • list_base_ratesFree

    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 detail on one.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

1 high1 low
  • Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 2170ms17/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
  • Maintenanceno repository listed3/15
  • Maintainer identityverified namespace with website, no repo4/10

Findings (2)

  • highWrite-action tools reachable without authenticationauth.open-write
  • lowNo source repository listedmaint.no-repo
Overall 56/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

claude mcp add --transport http quiet-failures https://mcp.quietfailures.com/mcp
Add to Cursor

Quiet Failures: common questions

Is Quiet Failures MCP server safe?
With care: it is graded C, so read the findings first (56/100). Read the Quiet Failures safety report
How do I install Quiet Failures?
It runs remotely at mcp.quietfailures.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Quiet Failures need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Quiet Failures maintained?
The latest release is v1.4.8.
Is Quiet Failures up?
100% of our last 20 checks got an answer. We check remote servers about four times a day.
What can I use instead of Quiet Failures?
Servers from other publishers that do the same job: Nel Veil MCP server, Prodcheck MCP server and prodlint MCP server. Compare all Quiet Failures alternatives.

Alternatives to Quiet Failures

Same job from other publishers: the closest match first, then the best rated.

All Quiet Failures alternatives →
  • Nel Veil
    Free passive security scanning - check any domain's DMARC, TLS, headers, and exposures.
    A
  • Prodcheck
    4,372 pre-production checks: security, performance, scale, integrations, post-launch.
    A
  • prodlint
    Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance.
    A
  • MCP
    Security tools for your AI: scan, pentest, check headers, guard code and scan repos for secrets.
    A
  • Nemesis Shield
    Positive-security for apps, APIs, LLMs and edge, plus fraud scoring and identity/AML screening.
    A

More from quietfailures.com