Remote MCP · Endpoint

AgentSEO MCP server

No. AgentSEO answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.agentseo.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.agentseo.www/agentseo-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
467 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Live SEO workflow tools for Claude Code, Codex, and AI agents.
Listing
From the official MCP registry (active).
Recent checks of AgentSEO
CheckedResultHandshake
1 hour agoHandshake completed467 ms
2 days agoHandshake completed121 ms
4 days agoHandshake completed235 ms
5 days agoHandshake completed220 ms
7 days agoHandshake completed208 ms
8 days agoHandshake completed216 ms
9 days agoHandshake completed107 ms
12 days agoHandshake completed913 ms
13 days agoHandshake completed285 ms
15 days agoHandshake completed214 ms
16 days agoHandshake completed240 ms
18 days agoHandshake completed303 ms
19 days agoHandshake completed154 ms
20 days agoHandshake completed214 ms
20 days agoHandshake completed133 ms
21 days agoHandshake completed265 ms
22 days agoHandshake completed203 ms

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

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