Remote MCP · Endpoint

com.jojapi/openai-sora MCP server

No. com.jojapi/openai-sora answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.jojapi.com/openai-sora

The last check completed an MCP handshake.

Registry name
com.jojapi/openai-sora
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
16 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
OpenAI Sora: Sora & Sora 2 (new social media like TikTok) API by ChatGPT creator OpenAI. Access.
Listing
From the official MCP registry (active).
Recent checks of com.jojapi/openai-sora
CheckedResultHandshake
1 hour agoHandshake completed52 ms
1 day agoHandshake completed49 ms
2 days agoHandshake completed58 ms

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

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