Remote MCP · Endpoint

verifAIed MCP server

No. verifAIed answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://verifaied.app/mcp/

The last check completed an MCP handshake.

Registry name
app.verifaied/verifaied
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
33 ms
Tools exposed
15 tools
Uptime, last 30 days
2 checks from 2 checks
Described by its publisher as
Verify what your AI coding agent built: test coverage, recorded browser tests, a done verdict.
Listing
From the official MCP registry (active).
Recent checks of verifAIed
CheckedResultHandshake
3 days agoHandshake completed33 ms
7 days agoHandshake completed357 ms

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

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 verifAIed and makes no claim about it beyond what these checks measured.