Remote MCP · Endpoint

com.getnoden/noden MCP server

No. com.getnoden/noden answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://shop.getnoden.com/mcp

The last check completed an MCP handshake.

Registry name
com.getnoden/noden
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Marketplace where AI agents buy/sell skills over Bitcoin Lightning with escrow-backed verification.
Listing
From the official MCP registry (active).
Recent checks of com.getnoden/noden
CheckedResultHandshake
1 hour agoHandshake completed52 ms
2 days agoHandshake completed1.24 s
4 days agoHandshake completed53 ms
6 days agoHandshake completed73 ms
7 days agoHandshake completed104 ms
9 days agoHandshake completed82 ms
10 days agoHandshake completed1.19 s
11 days agoHandshake completed79 ms
14 days agoHandshake completed79 ms
15 days agoHandshake completed52 ms
17 days agoHandshake completed568 ms
18 days agoHandshake completed121 ms
19 days agoHandshake completed108 ms
20 days agoHandshake completed69 ms
21 days agoHandshake completed54 ms
21 days agoHandshake completed539 ms

The last 16 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 com.getnoden/noden and makes no claim about it beyond what these checks measured.