Remote MCP · Endpoint

Pagemd MCP server

No. Pagemd answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pagemd.kaneky.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kaneky/pagemd
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
463 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Read any public web page as clean Markdown for LLMs, with its metadata. Paid per call, x402.
Listing
From the official MCP registry (active).
Recent checks of Pagemd
CheckedResultHandshake
1 hour agoHandshake completed463 ms
2 days agoHandshake completed434 ms
4 days agoHandshake completed425 ms
6 days agoHandshake completed405 ms
7 days agoHandshake completed409 ms
9 days agoHandshake completed582 ms
10 days agoHandshake completed1.94 s
11 days agoHandshake completed406 ms
14 days agoHandshake completed413 ms
15 days agoHandshake completed399 ms
17 days agoHandshake completed451 ms
18 days agoHandshake completed423 ms
19 days agoHandshake completed397 ms
20 days agoHandshake completed396 ms
21 days agoHandshake completed472 ms
21 days agoHandshake completed403 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 Pagemd and makes no claim about it beyond what these checks measured.