OneOver
REMOTE · API.ONEOVER.COM
Chat, image, video, and audio models from many vendors behind one remote MCP server and one key.
Available components
Last scanned (7 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- 71% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 944 tokens (~39/item across 24 items; 18 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability check failed: schema churn in the 16 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 44 to 47.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 41.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 31.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 14 to 17.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 1 to 4.
- 21 Oct 26 +3
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 2.0.0 ▼ security
- Tool “create_topup” was removed ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Tool “build_publish” is now declared destructive security
- Tool “build_stop” is now declared destructive security
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-03-26 → 2025-11-25 functional
- Tool “build_publish” changed its title: Publish a build to an unlisted link → Publish a build cosmetic
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 5 Nov 2026 · Probed https://api.oneover.com/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.oneover.com | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | dbd914faf0b3b9a5138d7bcb49d5011b |
| SANs: api.oneover.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 api.oneover.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oneover.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://oneover.com/.well-known/oauth-protected-resource", scope="mcp"
Bearer resource_metadata="https://oneover.com/.well-known/oauth-protected-resource", scope="mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Document | https://oneover.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.oneover.com/functions/v1/mcp |
| Authorisation server | https://oneover.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.oneover.com/functions/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.oneover.com/functions/v1/mcp | HTTPS enforced | 301 | https://api.oneover.com/functions/v1/mcp |
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 →
build_create Start a Code Studio build ~106
Start a Code Studio build: describe a page or small web app and OneOver writes the files. Returns build_id and build_project_id right away; the build keeps running. If a build card is shown it updates itself. Otherwise poll with build_status. The finished page is saved to the account library.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Optional model id. Defaults to build-default. |
| prompt | string | yes | What to build |
| title | string | – | Optional name for the project |
No output schema declared.
No examples provided.
build_get_files Read build files ~39
Read the files of a build. Pass path to read one file.
| Name | Type | Req | Description |
|---|---|---|---|
| build_project_id | string | yes | – |
| path | string | – | – |
No output schema declared.
No examples provided.
build_iterate Iterate on a Code Studio build ~54
Send a follow-up instruction to an existing build. Only one build can run on a project at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| build_project_id | string | yes | – |
| model | string | – | – |
| prompt | string | yes | – |
No output schema declared.
No examples provided.
build_publish Publish a build ~39
Publish a build to an unlisted share link at oneover.com/p/<slug>. Needs an HTML file.
| Name | Type | Req | Description |
|---|---|---|---|
| build_project_id | string | yes | – |
No output schema declared.
No examples provided.
build_status Check a build ~44
State of a build: running, complete, failed or stopped, plus file list, credits charged, and the share link once published.
| Name | Type | Req | Description |
|---|---|---|---|
| build_project_id | string | yes | – |
No output schema declared.
No examples provided.
build_stop Stop a build ~41
Stop a running build. Files already written are kept. Safe to call twice.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | build_id from build_create or build_iterate |
No output schema declared.
No examples provided.
chat Chat with a model ~46
Stateless chat completion across any text model in your org catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | number | – | – |
| messages | array | yes | Conversation turns |
| model | string | yes | Text model ID |
No output schema declared.
No examples provided.
check_video Check video job status ~52
Poll a video job until complete or failed. Shows text only. Do not call it repeatedly while a video card is on screen, because that card updates itself.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | UUID from generate_video |
No output schema declared.
No examples provided.
create_run Start a durable run ~57
Start a durable OneOver run. It keeps going after the client disconnects. Poll with get_run.
| Name | Type | Req | Description |
|---|---|---|---|
| background | boolean | – | – |
| input | object | – | – |
| modality | string | – | – |
| model | string | – | – |
No output schema declared.
No examples provided.
generate_audio Generate speech or music ~51
Generate speech or music audio.
| Name | Type | Req | Description |
|---|---|---|---|
| audio_kind | string | – | – |
| duration_seconds | number | – | – |
| model | string | yes | – |
| prompt | string | yes | – |
| voice | string | – | – |
No output schema declared.
No examples provided.
generate_image Generate an image ~55
Generate an image from a text prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | – |
| model | string | yes | – |
| negative_prompt | string | – | – |
| prompt | string | yes | – |
| resolution_tier | string | – | – |
No output schema declared.
No examples provided.
generate_video Generate a video ~99
Submit an async video generation job. Returns request_id. If a video card is shown it updates itself and you do not need to poll. Otherwise poll with check_video.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | – |
| duration | number | – | – |
| generate_audio | boolean | – | – |
| model | string | yes | – |
| prompt | string | – | – |
| reference_image | string | – | Base64-encoded image |
| resolution | string | – | – |
No output schema declared.
No examples provided.
get_job Check a generation job ~25
Poll a unified generation job by request_id.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
get_run Read a run ~34
Read a durable run and the events after a cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| after | number | – | – |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
get_usage Get credit balance and usage ~37
Get org credit balance or usage reporting.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
| limit | number | – | – |
| view | string | – | – |
No output schema declared.
No examples provided.
list_assets List library assets ~21
List API-generated library assets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
list_models List available models ~22
List models visible to your organization.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | – |
No output schema declared.
No examples provided.
run_app Run a OneOver app ~46
Run a Play app (upscale, transform, etc.) against a prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | – |
| model | string | – | – |
| prompt | string | yes | – |
No output schema declared.
No examples provided.
How do I install the OneOver MCP server?
OneOver is a hosted endpoint at https://api.oneover.com/functions/v1/mcp, 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 · api.oneover.com
claude mcp add --transport http com-oneover-mcp 'https://api.oneover.com/functions/v1/mcp'
What is the OneOver MCP server?
OneOver is an MCP server listed in the public MCP registry as com.oneover/mcp. Chat, image, video, and audio models from many vendors behind one remote MCP server and one key. This page covers its hosted endpoint (https://api.oneover.com/functions/v1/mcp).
Is the OneOver MCP server safe to use?
OneOver scores 81 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 OneOver MCP server expose?
OneOver exposes 18 tools: chat, generate_image, generate_video, check_video, generate_audio, and 13 more. Their descriptions and schemas cost roughly 868 tokens of context every time the server is loaded.
Does the OneOver MCP server require authentication?
Yes. OneOver asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the OneOver MCP server still maintained?
OneOver is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.