Remote MCP · Endpoint

AIGROW MCP server

No. AIGROW answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aigrow.gg/mcp

The last check completed an MCP handshake.

Registry name
gg.aigrow/ai-visibility
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
731 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Does AI recommend a business? The free AI visibility scan and the AI Visibility Index, by AIGROW.
Website
https://aigrow.gg/mcp
Listing
From the official MCP registry (active).
Recent checks of AIGROW
CheckedResultHandshake
1 hour agoHandshake completed731 ms
2 days agoHandshake completed424 ms
5 days agoHandshake completed426 ms
7 days agoHandshake completed429 ms
9 days agoHandshake completed479 ms
11 days agoHandshake completed497 ms
13 days agoHandshake completed148 ms
15 days agoHandshake completed145 ms
17 days agoHandshake completed422 ms
19 days agoHandshake completed388 ms
20 days agoHandshake completed445 ms
21 days agoHandshake completed1.59 s
23 days agoHandshake completed161 ms

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

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