Remote MCP · Endpoint

com.seoapi/meta MCP server

No. com.seoapi/meta answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://meta.seoapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.seoapi/meta
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
1 tool
Uptime, last 30 days
82.4% from 17 checks
Described by its publisher as
Validate Meta-ExternalAgent and Meta-WebIndexer IP addresses. Remote MCP validate_ip tool.
Listing
From the official MCP registry (active).
Recent checks of com.seoapi/meta
CheckedResultHandshake
1 hour agoHandshake completed68 ms
2 days agoHandshake completed52 ms
4 days agoFailed - the check failed for an unclassified reason—
5 days agoFailed - the check failed for an unclassified reason—
7 days agoHandshake completed40 ms
8 days agoHandshake completed315 ms
9 days agoHandshake completed56 ms
12 days agoFailed - the check failed for an unclassified reason—
13 days agoHandshake completed57 ms
15 days agoHandshake completed40 ms
16 days agoHandshake completed74 ms
17 days agoHandshake completed33 ms
19 days agoHandshake completed30 ms
20 days agoHandshake completed43 ms
20 days agoHandshake completed45 ms
21 days agoHandshake completed37 ms
22 days agoHandshake completed56 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 com.seoapi/meta and makes no claim about it beyond what these checks measured.