Remote MCP · Endpoint

Listen Notes MCP server

No. Listen Notes answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/listen-notes/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/listen-notes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
51 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Listen Notes MCP.
Listing
From the official MCP registry (active).
Recent checks of Listen Notes
CheckedResultHandshake
1 hour agoHandshake completed67 ms
1 day agoHandshake completed453 ms
2 days agoHandshake completed76 ms
3 days agoHandshake completed102 ms
4 days agoHandshake completed152 ms
5 days agoHandshake completed67 ms
6 days agoHandshake completed754 ms
9 days agoHandshake completed216 ms
12 days agoHandshake completed51 ms
14 days agoHandshake completed86 ms
16 days agoHandshake completed70 ms
18 days agoHandshake completed56 ms
21 days agoHandshake completed157 ms
23 days agoHandshake completed55 ms
25 days agoHandshake completed56 ms
26 days agoHandshake completed58 ms
28 days agoHandshake completed51 ms
29 days agoHandshake completed178 ms

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

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