Remote MCP · Endpoint

SEOReport MCP server

No. SEOReport answered an MCP handshake 1 hour ago.

Up · key neededLast checked 1 hour ago

Server URL

https://seoreport.dev/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
dev.seoreport/seoreport
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
88 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Run full technical SEO audits of any website from your AI agent and get structured findings back.
Listing
From the official MCP registry (active).
Recent checks of SEOReport
CheckedResultHandshake
1 hour agoHandshake completed88 ms
1 day agoHandshake completed205 ms
2 days agoHandshake completed87 ms
3 days agoHandshake completed81 ms
4 days agoHandshake completed92 ms
5 days agoHandshake completed73 ms
6 days agoHandshake completed740 ms
9 days agoHandshake completed126 ms
11 days agoHandshake completed91 ms
14 days agoHandshake completed119 ms
16 days agoHandshake completed95 ms
18 days agoHandshake completed327 ms
20 days agoHandshake completed129 ms
22 days agoHandshake completed197 ms
24 days agoHandshake completed71 ms

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

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