Remote MCP · Endpoint

io.github.cmdenney/logicnodes-mcp MCP server

No. io.github.cmdenney/logicnodes-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://logicnodes.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.cmdenney/logicnodes-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
389 ms
Tools exposed
2 tools
Uptime, last 30 days
72.2% from 18 checks
Described by its publisher as
Remote MCP for LogicNodes: Signed PII-Shield flagship + payable x402 agent tools on Base.
Listing
From the official MCP registry (active).
Recent checks of io.github.cmdenney/logicnodes-mcp
CheckedResultHandshake
1 hour agoHandshake completed389 ms
1 day agoHandshake completed385 ms
3 days agoHandshake completed382 ms
3 days agoHandshake completed391 ms
4 days agoHandshake completed383 ms
5 days agoHandshake completed362 ms
7 days agoHandshake completed381 ms
10 days agoHandshake completed399 ms
12 days agoHandshake completed417 ms
15 days agoHandshake completed369 ms
17 days agoHandshake completed451 ms
19 days agoHandshake completed472 ms
21 days agoHandshake completed1.71 s
23 days agoFailed - the request timed out—
25 days agoFailed - the request timed out—
26 days agoFailed - the request timed out—
28 days agoFailed - the request timed out—
29 days agoFailed - the request timed out—

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 io.github.cmdenney/logicnodes-mcp and makes no claim about it beyond what these checks measured.