Remote MCP · Endpoint

Surfacing Feelings MCP server

No. Surfacing Feelings answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://surfacing-mcp.knightcorrick.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
com.surfacingapp/feelings
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Helps people name what they feel: 796 feeling words and a body map of 243 sensations.
Listing
From the official MCP registry (active).
Recent checks of Surfacing Feelings
CheckedResultHandshake
1 hour agoHandshake completed49 ms
2 days agoHandshake completed80 ms
5 days agoHandshake completed87 ms
7 days agoHandshake completed67 ms
9 days agoHandshake completed71 ms
11 days agoHandshake completed2.36 s
13 days agoHandshake completed54 ms
15 days agoHandshake completed41 ms
17 days agoHandshake completed43 ms
18 days agoHandshake completed82 ms
19 days agoHandshake completed266 ms
20 days agoHandshake completed31 ms
23 days agoHandshake completed48 ms
25 days agoHandshake completed93 ms

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

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