Agent Tools
List
Back to MCP servers

Go-Live Check

https://dontdeployonfriday.com/mcp
● healthy

Checks HTTP response headers you paste: 7 security checks with copy-paste fixes. No fetching.

What we measured

Over the last 30 days we probed this MCP server 25 times on 24 days; it answered 25 (100%). Median response 422 ms, 95th percentile 457 ms.

When we called tools/list it returned 4 tools, including analyze_headers, explain_finding, get_fix, over MCP protocol revision 2025-06-18.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 45% and higher on readiness than 60%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (4)

As returned by the server's own tools/list when we called it.

analyze_headers
Check raw HTTP response headers from a deployment you already operate. Returns the same object as POST /v1/analyze. Unknown fields are ignored. A url field is n…
explain_finding
Explain one finding id from the seven. Returns id, severity, why, and answer_page. answer_page is the CSP and clickjacking page for GLC-CSP-MISSING and GLC-FRAM…
get_fix
Return the registry snippet for one finding id and one platform. The platforms are caddy, nginx, vercel, netlify, nextjs. The result is id and fix. fix has plat…
report_feedback
Report one finding id and one outcome. The outcomes are false_positive, fix_worked, fix_failed. The result is id, outcome, and stored false. Nothing is written:…
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-06-18
negotiated, not declared

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B+, 89.9/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (448 ms).
Protocol revision 6/10 Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 25/25 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 4 tool(s) with descriptions.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 2/5 seen within 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (448 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-12.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness
Higher than 60% of peers
This listing 83 · peer median 81
Latency
Faster than 45% of peers
This listing 398 ms · peer median 349 ms

Where it loses the most points, and how to win them back

  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Protocol revision −4 — Support the current protocol revision.
    Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
  • Verified identity −3 — Claim the listing and prove control of its domain.
    Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-10-20 capkey since 2026-10-26 ↗

How to connect

MCP endpoint (streamable-http)
https://dontdeployonfriday.com/mcp
JSON-RPC initialize probe
curl -X POST https://dontdeployonfriday.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://dontdeployonfriday.com