Remote MCP · Endpoint

NodeProxy Web Surface Markdown Parser MCP server

No. NodeProxy Web Surface Markdown Parser answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nodeproxy-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.pgalyen1987/nodeproxy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
95 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
x402 MCP web parser: URLs to Markdown for agents. USDC on Base, Polygon, Arbitrum, Ethereum.
Listing
From the official MCP registry (active).
Recent checks of NodeProxy Web Surface Markdown Parser
CheckedResultHandshake
1 hour agoHandshake completed95 ms
1 day agoHandshake completed115 ms
2 days agoHandshake completed96 ms
3 days agoHandshake completed99 ms
4 days agoHandshake completed119 ms
5 days agoHandshake completed106 ms
6 days agoHandshake completed98 ms
9 days agoHandshake completed92 ms
11 days agoHandshake completed96 ms
14 days agoHandshake completed91 ms
16 days agoHandshake completed102 ms
18 days agoHandshake completed97 ms
20 days agoHandshake completed125 ms
22 days agoHandshake completed93 ms
24 days agoHandshake completed95 ms
26 days agoHandshake completed115 ms
28 days agoHandshake completed130 ms
29 days agoHandshake completed595 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 NodeProxy Web Surface Markdown Parser and makes no claim about it beyond what these checks measured.