Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ViewMax MCP

REMOTE · VIEWMAXSTUDIO.NET

Generate AI video from any MCP client. Pick the model, see the per-second price before you spend.

0 this week 78 Trust /100

Last scanned (16 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 747 tokens (~186/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Oct 26 +2
    • HSTS header: fail → pass ▲ security
  • 10 Oct 26 0
    • Stability: 0.80 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://viewmaxstudio.net/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=viewmaxstudio.net CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 44d9008c1ce186850ee2e15ed0d01306
SANs: viewmaxstudio.net, *.viewmaxstudio.net
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 viewmaxstudio.net. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
net. DS published 37331 13 Verified
viewmaxstudio.net. No DS 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
Header Value
strict-transport-security max-age=15552000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://viewmaxstudio.net/api/mcp Verified 200
http (plaintext) http://viewmaxstudio.net/api/mcp HTTPS enforced 301 https://viewmaxstudio.net/api/mcp
MCP tools · 4 exposed · ~682 tokens

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 →

Tool Tokens
generate_video ~473

Render a video from a text prompt using ViewMax Studio. Returns immediately with a job id; the clip is not ready yet. Rendering takes roughly two to four minutes. Call `get_video` with the returned id to collect the result, waiting about 15 seconds between checks. Do not poll faster than that, and tell the user it is rendering rather than going silent while you wait. Credits are charged to the account the API key belongs to, and refunded automatically if the render fails. Available models: - seedance-2-mini: Native audio and multi-shot cuts in one clip. Longest takes we offer. (4–15s, 480p/720p/1080p, with audio) - h3-max: Native 768p with no upscale pass. Fastest turnaround, up to 15s takes. (5–15s, 480p/768p, with audio) - h3-max-turbo: Half the price of H3 Max at the same sizes, and the quickest render we carry. (5–15s, 480p/768p, with audio) - viewmax-agent-2.0: Writes, cuts and scores a whole video from one brief, at any length you ask for. (15s and up, 720p, with audio) Leave `model` unset to use the default. Call `list_video_models` if you need exact per-model limits or prices.

NameTypeReqDescription
aspectRatiostring–Frame shape. Use "9:16" for phone-first platforms, "16:9" for landscape, "21:9" for cinematic.
durationstring–Clip length in seconds, as a string, e.g. "5". Which lengths are accepted depends on the model.
generateAudioboolean–Whether a model that renders its own soundtrack should. Ignored by silent models.
modelstring–Which model renders it. Omit for the default model.
negativePromptstring–What to keep out of the clip. Optional.
promptstringyesWhat the clip should show. Describe subject, action, camera move and lighting; vague prompts render poorly.
resolutionstring–Output resolution. Larger costs proportionally more.

No output schema declared.

No examples provided.

get_credit_balance ~41

How many ViewMax Studio credits the API key holder has left. Worth checking before booking an expensive render, since one that cannot be paid for is refused outright.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_video ~99

Look up a render started by `generate_video`. While `status` is "pending" or "processing" the clip is still being made, so wait about 15 seconds and check again. When it is "completed" the result carries a public URL anyone can open, which you should hand the user directly. When it is "failed" the credits have already been refunded.

NameTypeReqDescription
idstringyesThe job id returned by `generate_video`.

No output schema declared.

No examples provided.

list_video_models ~69

Every video model on offer with its exact limits and credit prices: which lengths, resolutions and frame shapes it accepts, whether it renders audio, how long it takes, and what a second of output costs. Use it to choose a model on price or capability, or to quote a cost before rendering.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the ViewMax MCP server?

ViewMax MCP is a hosted endpoint at https://viewmaxstudio.net/api/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 · viewmaxstudio.net

# add to Claude Code
claude mcp add --transport http net-viewmaxstudio-viewmax 'https://viewmaxstudio.net/api/mcp'
Common questions

What is the ViewMax MCP server?

ViewMax MCP is listed in the public MCP registry as net.viewmaxstudio/viewmax. Generate AI video from any MCP client. Pick the model, see the per-second price before you spend. This page covers its hosted endpoint (https://viewmaxstudio.net/api/mcp).

Is the ViewMax MCP server safe to use?

ViewMax MCP scores 78 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 ViewMax MCP server expose?

ViewMax MCP exposes 4 tools: generate_video, get_video, get_credit_balance, list_video_models. Their descriptions and schemas cost roughly 682 tokens of context every time the server is loaded.

Does the ViewMax MCP server require authentication?

No. We connected to ViewMax MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ViewMax MCP server still maintained?

ViewMax MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ViewMax MCP server?

VerifyMCP ran 12 checks on ViewMax MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ViewMax MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.