Remote MCP · Endpoint

GEO-bot MCP server

No. GEO-bot answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://feelswebman.com/projects/geo-bot/mcp.php

The last check completed an MCP handshake.

Registry name
com.feelswebman/geo-bot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
367 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free check whether a website is technically open to AI assistants (AI crawlers, llms.txt, JSON-LD).
Listing
From the official MCP registry (active).
Recent checks of GEO-bot
CheckedResultHandshake
1 hour agoHandshake completed367 ms
4 days agoHandshake completed386 ms
14 days agoHandshake completed603 ms
15 days agoHandshake completed359 ms
15 days agoHandshake completed373 ms
17 days agoHandshake completed349 ms
18 days agoHandshake completed351 ms
19 days agoHandshake completed344 ms
20 days agoHandshake completed355 ms
21 days agoHandshake completed373 ms
23 days agoHandshake completed367 ms
25 days agoHandshake completed355 ms
28 days agoHandshake completed357 ms

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

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