Remote MCP · Endpoint

ECAC: DCTF WEB MCP server

No. ECAC: DCTF WEB answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_ecac_dctf_web

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/ecac_dctf_web-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
ECAC: DCTF WEB, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Listing
From the official MCP registry (active).
Recent checks of ECAC: DCTF WEB
CheckedResultHandshake
1 day agoHandshake completed49 ms
3 days agoHandshake completed30 ms
5 days agoHandshake completed769 ms
7 days agoHandshake completed62 ms
8 days agoHandshake completed43 ms
9 days agoHandshake completed128 ms
12 days agoHandshake completed82 ms
13 days agoHandshake completed106 ms
15 days agoHandshake completed72 ms
16 days agoHandshake completed36 ms
18 days agoHandshake completed70 ms
19 days agoHandshake completed125 ms
20 days agoHandshake completed75 ms
20 days agoHandshake completed79 ms
21 days agoHandshake completed76 ms
23 days agoHandshake completed114 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with ECAC: DCTF WEB and makes no claim about it beyond what these checks measured.