Remote MCP · Endpoint

seoskills.sh MCP server

No. seoskills.sh answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://seoskills.sh/api/mcp

The last check completed an MCP handshake.

Registry name
sh.seoskills/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search and fetch SEO agent skills from the seoskills.sh catalog.
Listing
From the official MCP registry (active).
Recent checks of seoskills.sh
CheckedResultHandshake
1 hour agoHandshake completed122 ms
1 day agoHandshake completed504 ms
2 days agoHandshake completed129 ms
3 days agoHandshake completed1.01 s
4 days agoHandshake completed122 ms
5 days agoHandshake completed117 ms
6 days agoHandshake completed1.01 s
9 days agoHandshake completed104 ms
11 days agoHandshake completed163 ms
14 days agoHandshake completed116 ms
16 days agoHandshake completed125 ms
18 days agoHandshake completed512 ms
20 days agoHandshake completed98 ms
22 days agoHandshake completed106 ms
24 days agoHandshake completed73 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 seoskills.sh and makes no claim about it beyond what these checks measured.