Remote MCP · Endpoint
io.github.thinksuitesolution-coder/visibilityai MCP server
No. io.github.thinksuitesolution-coder/visibilityai answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://visibilityai.in/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.thinksuitesolution-coder/visibilityai
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 410 ms
- Tools exposed
- 24 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Verified Indian business data and AI-visibility reports for MCP-compatible AI agents.
- Website
- https://visibilityai.in/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 410 ms |
| 1 day ago | Handshake completed | 338 ms |
| 2 days ago | Handshake completed | 285 ms |
| 3 days ago | Handshake completed | 337 ms |
| 4 days ago | Handshake completed | 267 ms |
| 5 days ago | Handshake completed | 255 ms |
| 6 days ago | Handshake completed | 271 ms |
| 8 days ago | Handshake completed | 396 ms |
| 11 days ago | Handshake completed | 314 ms |
| 13 days ago | Handshake completed | 364 ms |
| 15 days ago | Handshake completed | 360 ms |
| 18 days ago | Handshake completed | 886 ms |
| 20 days ago | Handshake completed | 358 ms |
| 22 days ago | Handshake completed | 254 ms |
| 24 days ago | Handshake completed | 373 ms |
| 26 days ago | Handshake completed | 1.66 s |
| 27 days ago | Handshake completed | 220 ms |
| 28 days ago | Handshake completed | 298 ms |
| 29 days ago | Handshake completed | 395 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 io.github.thinksuitesolution-coder/visibilityai and makes no claim about it beyond what these checks measured.