com.jojapi/openai-sora
REMOTE · MCP.JOJAPI.COM · SCANNED SEP 20
OpenAI Sora: Sora & Sora 2 (new social media like TikTok) API by ChatGPT creator OpenAI. Access.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1323 tokens (~82/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.jojapi/openai-sora MCP server?
com.jojapi/openai-sora is a hosted endpoint at https://mcp.jojapi.com/openai-sora, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.jojapi.com
claude mcp add --transport http com-jojapi-openai-sora 'https://mcp.jojapi.com/openai-sora'
{
"mcpServers": {
"com-jojapi-openai-sora": {
"url": "https://mcp.jojapi.com/openai-sora"
}
}
} {
"servers": {
"com-jojapi-openai-sora": {
"type": "http",
"url": "https://mcp.jojapi.com/openai-sora"
}
}
} [mcp_servers.com-jojapi-openai-sora] url = "https://mcp.jojapi.com/openai-sora"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-jojapi-openai-sora": {
"type": "remote",
"url": "https://mcp.jojapi.com/openai-sora",
"enabled": true
}
}
} openclaw mcp add com-jojapi-openai-sora --url 'https://mcp.jojapi.com/openai-sora' --transport streamable-http
mcp_servers:
com-jojapi-openai-sora:
url: "https://mcp.jojapi.com/openai-sora" {
"McpServers": {
"com-jojapi-openai-sora": {
"Transport": "http",
"Url": "https://mcp.jojapi.com/openai-sora"
}
}
} assistant mcp add com-jojapi-openai-sora -t streamable-http -u 'https://mcp.jojapi.com/openai-sora'
{
"mcpServers": {
"com-jojapi-openai-sora": {
"type": "http",
"url": "https://mcp.jojapi.com/openai-sora"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.jojapi.com/openai-sora
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.jojapi.com | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6bf56e5f5706ef0d0eece5dccb581199 |
| SANs: mcp.jojapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.jojapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jojapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.jojapi.com/openai-sora | Verified | 200 | |
| http (plaintext) | http://mcp.jojapi.com/openai-sora | HTTPS enforced | 301 | https://mcp.jojapi.com/openai-sora |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_v1_feed_home v1 / Home Feed ~90
v1 / Home Feed Group: v1 Endpoint (Old Sora App). Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | You can get subsequent results by entering the `last_id` value taken from the first response. |
| limit | string | – | Result limit |
| task_type_filters | string | – | Filter results. To get all results, don't send this parameter. |
No output schema declared.
No examples provided.
get_v1_feed_images v1 / Images Feed ~69
v1 / Images Feed Group: v1 Endpoint (Old Sora App). Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | You can get subsequent results by entering the `last_id` value taken from the first response. |
| limit | string | – | Result limit |
No output schema declared.
No examples provided.
get_v1_feed_top v1 / Top Feed ~100
v1 / Top Feed Group: v1 Endpoint (Old Sora App). Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | You can get subsequent results by entering the `last_id` value taken from the first response. |
| limit | string | – | Result limit |
| task_type_filters | string | – | Filter results. To get all results, don't send this parameter. |
| time_range | string | – | Time range |
No output schema declared.
No examples provided.
get_v1_feed_videos v1 / Videos Feed ~70
v1 / Videos Feed Group: v1 Endpoint (Old Sora App). Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | You can get subsequent results by entering the `last_id` value taken from the first response. |
| limit | string | – | Result limit |
No output schema declared.
No examples provided.
get_v1_post_details v1 / Post Details ~46
v1 / Post Details Group: v1 Endpoint (Old Sora App). Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| generation_id | string | – | Allowed Generation ID |
No output schema declared.
No examples provided.
get_v1_profile_details v1 / Profile Details ~46
v1 / Profile Details Group: v1 Endpoint (Old Sora App). Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | Allowed User ID |
No output schema declared.
No examples provided.
get_v1_search v1 / Search ~113
v1 / Search Group: v1 Endpoint (Old Sora App). Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | You can get subsequent results by entering the `last_id` value taken from the first response. |
| query | string | – | Search query |
| similar_to | string | – | Search for similar content. An array containing Generation IDs (`gen_...`) must be sent. |
| user_id | string | – | Fetch content from a specific user. Allowed User ID or username. |
No output schema declared.
No examples provided.
get_v2_feed v2 / Feed ~122
v2 / Feed Group: v2 / Explore. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | You can get subsequent results by entering the `cursor` value taken from the first response. |
| cut | string | – | Sorting parameter. Default is `nf2`. What does it mean? : - `nf2` : For you (You can assume that it brings random popular videos.) - `nf2_top` : Top videos - `nf2_latest` : Latest videos |
| limit | string | – | Result limit |
No output schema declared.
No examples provided.
get_v2_post_details_and_replies v2 / Post Details & Replies ~112
v2 / Post Details & Replies Group: v2 / Post. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | You can get subsequent results by entering the `cursor` value taken from the first response. |
| limit | string | – | Result limit |
| max_depth | string | – | Tree depth for replies. Default = 1 |
| post_id | string | – | Post ID (You can also enter the Child ID to get sub-replies to a reply.) |
No output schema declared.
No examples provided.
get_v2_post_remix_feed v2 / Post Remix Feed ~68
v2 / Post Remix Feed Group: v2 / Post. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | You can get subsequent results by entering the `cursor` value taken from the first response. |
| post_id | string | – | Post ID |
No output schema declared.
No examples provided.
get_v2_profile_cameos v2 / Profile Cameos ~77
v2 / Profile Cameos Group: v2 / Profile. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | You can get subsequent results by entering the `cursor` value taken from the first response. |
| limit | string | – | Result limit |
| user_id | string | – | User ID |
No output schema declared.
No examples provided.
get_v2_profile_details v2 / Profile Details ~39
v2 / Profile Details Group: v2 / Profile. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | – | Username |
No output schema declared.
No examples provided.
get_v2_profile_feed v2 / Profile Feed (Posts) ~77
v2 / Profile Feed (Posts) Group: v2 / Profile. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | You can get subsequent results by entering the `cursor` value taken from the first response. |
| limit | string | – | Result limit |
| user_id | string | – | User ID |
No output schema declared.
No examples provided.
get_v2_profile_followers v2 / Profile Followers ~75
v2 / Profile Followers Group: v2 / Profile. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | You can get subsequent results by entering the `cursor` value taken from the first response. |
| limit | string | – | Result limit |
| user_id | string | – | User ID |
No output schema declared.
No examples provided.
get_v2_profile_following v2 / Profile Following ~75
v2 / Profile Following Group: v2 / Profile. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | You can get subsequent results by entering the `cursor` value taken from the first response. |
| limit | string | – | Result limit |
| user_id | string | – | User ID |
No output schema declared.
No examples provided.
get_v2_search v2 / Search ~49
v2 / Search Group: v2 / Explore. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Result limit |
| username | string | – | Search query for users |
No output schema declared.
No examples provided.
What is the com.jojapi/openai-sora MCP server?
com.jojapi/openai-sora is an MCP server listed in the public MCP registry as com.jojapi/openai-sora. OpenAI Sora: Sora & Sora 2 (new social media like TikTok) API by ChatGPT creator OpenAI. Access. This page covers its hosted endpoint (https://mcp.jojapi.com/openai-sora).
Is the com.jojapi/openai-sora MCP server safe to use?
com.jojapi/openai-sora scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.jojapi/openai-sora MCP server expose?
com.jojapi/openai-sora exposes 16 tools: get_v2_feed, get_v2_search, get_v2_profile_details, get_v2_profile_feed, get_v2_profile_cameos, and 11 more. Their descriptions and schemas cost roughly 1,228 tokens of context every time the server is loaded.
Does the com.jojapi/openai-sora MCP server require authentication?
No. We connected to com.jojapi/openai-sora without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.jojapi/openai-sora MCP server still maintained?
com.jojapi/openai-sora is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.