Remote MCP · Endpoint

dev.ecoa/ecoa MCP server

No. dev.ecoa/ecoa answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.ecoa.dev/api/mcp/public

The last check completed an MCP handshake.

Registry name
dev.ecoa/ecoa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
207 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verificação de segurança e conformidade de sites: cabeçalhos, TLS, DNS, e-mail, LGPD e pentest.
Website
https://ecoa.dev/
Repository
https://github.com/ecoa-org/ecoa
Listing
From the official MCP registry (active).
Recent checks of dev.ecoa/ecoa
CheckedResultHandshake
1 hour agoHandshake completed207 ms
2 days agoHandshake completed180 ms
4 days agoHandshake completed106 ms
5 days agoHandshake completed161 ms
7 days agoHandshake completed213 ms
8 days agoHandshake completed428 ms
9 days agoHandshake completed119 ms
12 days agoHandshake completed102 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed186 ms
16 days agoHandshake completed178 ms
18 days agoHandshake completed121 ms
19 days agoHandshake completed131 ms
20 days agoHandshake completed122 ms
20 days agoHandshake completed128 ms
21 days agoHandshake completed139 ms
22 days agoHandshake completed176 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with dev.ecoa/ecoa and makes no claim about it beyond what these checks measured.