Remote MCP · Endpoint

FeelingSurf MCP server

No. FeelingSurf answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.feelingsurf.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.feelingsurf/feelingsurf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
34 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Manage your FeelingSurf traffic exchange account: sites, targeting, templates, sources and proxies.
Listing
From the official MCP registry (active).
Recent checks of FeelingSurf
CheckedResultHandshake
1 hour agoHandshake completed290 ms
2 days agoHandshake completed268 ms
4 days agoHandshake completed324 ms
6 days agoHandshake completed277 ms
9 days agoHandshake completed295 ms
11 days agoHandshake completed297 ms
13 days agoHandshake completed399 ms
15 days agoHandshake completed266 ms
17 days agoHandshake completed264 ms
19 days agoHandshake completed257 ms
20 days agoHandshake completed252 ms
22 days agoHandshake completed267 ms
23 days agoFailed - the server returned an HTTP error—

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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.

Listing data comes from the official MCP registry. Glide is not affiliated with FeelingSurf and makes no claim about it beyond what these checks measured.