Remote MCP · Endpoint

OnPage.dev MCP server

No. OnPage.dev answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
242 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 13 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
1 hour agoHandshake completed242 ms
2 days agoHandshake completed344 ms
5 days agoHandshake completed149 ms
7 days agoHandshake completed455 ms
9 days agoHandshake completed162 ms
11 days agoHandshake completed162 ms
13 days agoHandshake completed146 ms
15 days agoHandshake completed134 ms
18 days agoHandshake completed117 ms
19 days agoHandshake completed138 ms
20 days agoHandshake completed179 ms
22 days agoHandshake completed562 ms
23 days agoHandshake completed40 ms

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

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.