Remote MCP · Endpoint
SEO Audit MCP Server MCP server
No. SEO Audit MCP Server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://seo.accruedev.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.glivera/seo-audit
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 404 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Professional SEO auditing: 15 tools, 9 checks, CWV, E-E-A-T, schema, GEO. Free tier.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 404 ms |
| 1 day ago | Handshake completed | 455 ms |
| 2 days ago | Failed - the request timed out | — |
| 3 days ago | Handshake completed | 414 ms |
| 4 days ago | Handshake completed | 417 ms |
| 5 days ago | Handshake completed | 169 ms |
| 6 days ago | Handshake completed | 900 ms |
| 9 days ago | Handshake completed | 447 ms |
| 11 days ago | Handshake completed | 409 ms |
| 14 days ago | Handshake completed | 462 ms |
| 16 days ago | Handshake completed | 467 ms |
| 18 days ago | Handshake completed | 420 ms |
| 20 days ago | Handshake completed | 5.70 s |
| 22 days ago | Handshake completed | 455 ms |
| 24 days ago | Handshake completed | 399 ms |
| 26 days ago | Handshake completed | 396 ms |
| 27 days ago | Handshake completed | 394 ms |
| 29 days ago | Handshake completed | 459 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 SEO Audit MCP Server and makes no claim about it beyond what these checks measured.