Remote MCP · Endpoint

AuditAE SEO MCP MCP server

No. AuditAE SEO MCP answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://auditae.app/api/mcp/pay

The last check completed an MCP handshake.

Registry name
app.auditae/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
41 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
SEO MCP: Search Console, GA4, SERP and domain data, rank tracking, AI citations and site fixes.
Listing
From the official MCP registry (active).
Recent checks of AuditAE SEO MCP
CheckedResultHandshake
2 hours agoHandshake completed142 ms
1 day agoHandshake completed147 ms
2 days agoHandshake completed385 ms
2 days agoHandshake completed179 ms
4 days agoHandshake completed117 ms
7 days agoHandshake completed122 ms
9 days agoHandshake completed257 ms
12 days agoHandshake completed174 ms
14 days agoHandshake completed126 ms
16 days agoHandshake completed215 ms
18 days agoHandshake completed168 ms
20 days agoHandshake completed121 ms
22 days agoHandshake completed126 ms
23 days agoHandshake completed363 ms

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

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