Remote MCP · Endpoint

AISOTools MCP server

No. AISOTools answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://aisotools.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.shibley/aisotools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
698 ms
Tools exposed
5 tools
Uptime, last 30 days
88.2% from 17 checks
Described by its publisher as
Search, compare, and find alternatives across a catalog of 3,000+ AI tools.
Listing
From the official MCP registry (active).
Recent checks of AISOTools
CheckedResultHandshake
2 hours agoHandshake completed698 ms
2 days agoHandshake completed64 ms
4 days agoFailed - the request timed out—
5 days agoHandshake completed58 ms
7 days agoHandshake completed80 ms
8 days agoHandshake completed299 ms
9 days agoHandshake completed80 ms
12 days agoHandshake completed70 ms
13 days agoHandshake completed355 ms
15 days agoHandshake completed67 ms
17 days agoFailed - the request timed out—
18 days agoHandshake completed52 ms
19 days agoHandshake completed61 ms
20 days agoHandshake completed73 ms
20 days agoHandshake completed81 ms
21 days agoHandshake completed267 ms
23 days agoHandshake completed284 ms

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

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