Remote MCP · Endpoint

Fenlight MCP server

No. Fenlight answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://fenlight.waggle.ae/mcp

The last check completed an MCP handshake.

Registry name
ae.waggle/fenlight
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
291 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Google search results, forum threads, local and shopping data, keyword ideas, AI answer tracking.
Listing
From the official MCP registry (active).
Recent checks of Fenlight
CheckedResultHandshake
3 hours agoHandshake completed291 ms
9 days agoHandshake completed271 ms
10 days agoHandshake completed355 ms
11 days agoHandshake completed273 ms
12 days agoHandshake completed270 ms
14 days agoHandshake completed295 ms
14 days agoHandshake completed271 ms
15 days agoHandshake completed298 ms
17 days agoHandshake completed282 ms
19 days agoHandshake completed280 ms
21 days agoHandshake completed271 ms
24 days agoHandshake completed284 ms
26 days agoHandshake completed279 ms
28 days agoHandshake completed309 ms

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

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