Remote MCP · Endpoint

WebAISEO - AI-search readiness check MCP server

No. WebAISEO - AI-search readiness check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://truetest.uk/mcp/ai-search

The last check completed an MCP handshake.

Registry name
uk.truetest/ai-search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
267 ms
Tools exposed
1 tool
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
FREE check: can AI search engines find, read and trust your web page? Fixes listed per page
Listing
From the official MCP registry (active).
Recent checks of WebAISEO - AI-search readiness check
CheckedResultHandshake
1 hour agoHandshake completed267 ms
4 days agoHandshake completed266 ms
7 days agoHandshake completed262 ms

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

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 WebAISEO - AI-search readiness check and makes no claim about it beyond what these checks measured.