Remote MCP · Endpoint

com.seoapi/openai MCP server

Yes, as of 2 hours ago: the check failed for an unclassified reason.

DownLast checked 2 hours ago

Server URL

https://openai.seoapi.com/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
com.seoapi/openai
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
55.6% from 18 checks
Described by its publisher as
Validate GPTBot and OAI-SearchBot IP addresses. Remote MCP validate_ip tool.
Listing
From the official MCP registry (active).
Recent checks of com.seoapi/openai
CheckedResultHandshake
2 hours agoFailed - the check failed for an unclassified reason—
1 day agoHandshake completed52 ms
2 days agoHandshake completed71 ms
3 days agoHandshake completed926 ms
4 days agoHandshake completed102 ms
5 days agoFailed - the check failed for an unclassified reason—
7 days agoHandshake completed82 ms
9 days agoHandshake completed86 ms
12 days agoFailed - the check failed for an unclassified reason—
14 days agoHandshake completed357 ms
16 days agoHandshake completed52 ms
18 days agoFailed - the check failed for an unclassified reason—
20 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
24 days agoFailed - the check failed for an unclassified reason—
26 days agoFailed - the check failed for an unclassified reason—
27 days agoHandshake completed37 ms
29 days agoHandshake completed316 ms

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

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