Remote MCP · Endpoint

GEO SEO Records MCP server

No. GEO SEO Records answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://api.seorecords.com/mcp/geo

The last check completed an MCP handshake.

Registry name
com.seorecords/geo-seo-records
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Gets a website ready for AI assistants: robots.txt fixed, llms.txt drafted (access pass).
Listing
From the official MCP registry (active).
Recent checks of GEO SEO Records
CheckedResultHandshake
19 minutes agoHandshake completed62 ms
10 days agoHandshake completed75 ms
10 days agoHandshake completed167 ms
11 days agoHandshake completed54 ms
13 days agoHandshake completed111 ms
14 days agoHandshake completed79 ms
14 days agoHandshake completed68 ms
15 days agoHandshake completed73 ms
17 days agoHandshake completed150 ms
19 days agoHandshake completed177 ms
21 days agoHandshake completed63 ms
24 days agoHandshake completed74 ms
26 days agoHandshake completed81 ms
28 days agoHandshake completed65 ms

The last 14 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 GEO SEO Records and makes no claim about it beyond what these checks measured.