Remote MCP · Endpoint

EffectHub MCP server

No. EffectHub answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://effecthub.net/api/mcp

The last check completed an MCP handshake.

Registry name
net.effecthub/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.22 s
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and compare 3,000+ checked AI tools: pricing, liveness, Effect and Trust scores.
Listing
From the official MCP registry (active).
Recent checks of EffectHub
CheckedResultHandshake
8 hours agoHandshake completed1.22 s
10 days agoHandshake completed767 ms
11 days agoHandshake completed425 ms
11 days agoHandshake completed345 ms
13 days agoHandshake completed352 ms
15 days agoHandshake completed353 ms
15 days agoHandshake completed343 ms
16 days agoHandshake completed369 ms
17 days agoHandshake completed360 ms
19 days agoHandshake completed356 ms
22 days agoHandshake completed371 ms
24 days agoHandshake completed345 ms
26 days agoHandshake completed376 ms
29 days agoHandshake completed336 ms

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

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