Remote MCP · Endpoint

AiSeek MCP server

No. AiSeek answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://aiseek.dev/api/v1/mcp

The last check completed an MCP handshake.

Registry name
dev.aiseek/aiseek
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
476 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verified world changes with sources: topics, companies, countries, SeekEarth and evidence receipts.
Website
https://aiseek.dev/en/developers#mcp
Listing
From the official MCP registry (active).
Recent checks of AiSeek
CheckedResultHandshake
3 hours agoHandshake completed476 ms
13 hours agoHandshake completed476 ms
2 days agoHandshake completed328 ms
4 days agoHandshake completed499 ms
7 days agoHandshake completed463 ms
9 days agoHandshake completed227 ms
11 days agoHandshake completed227 ms
14 days agoHandshake completed592 ms
15 days agoHandshake completed707 ms
18 days agoHandshake completed204 ms
20 days agoHandshake completed593 ms
21 days agoHandshake completed637 ms
23 days agoHandshake completed587 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 AiSeek and makes no claim about it beyond what these checks measured.