Remote MCP · Endpoint

OnPage.dev MCP server

No. OnPage.dev answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://onpage.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.onpage/onpage
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
199 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free SEO MCP that closes the loop: find, fix, ship as a PR or to a CMS, prove. 37 tools, no key.
Listing
From the official MCP registry (active).
Recent checks of OnPage.dev
CheckedResultHandshake
6 hours agoHandshake completed199 ms
3 days agoHandshake completed292 ms
12 days agoHandshake completed185 ms
13 days agoHandshake completed224 ms
14 days agoHandshake completed216 ms
15 days agoHandshake completed354 ms
16 days agoHandshake completed277 ms
17 days agoHandshake completed63 ms
18 days agoHandshake completed261 ms
20 days agoHandshake completed242 ms
22 days agoHandshake completed344 ms
25 days agoHandshake completed149 ms
27 days agoHandshake completed455 ms
29 days agoHandshake completed162 ms

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

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