ViewMax MCP
io.github.bytevirts/viewmax
Remote MCP for AI video, image, music and speech generation.
— the operator's own registry description reported
Publisher io.github.bytevirts · first seen 2026-08-16 · endpoint https://viewmax.studio/api/mcp
Dependency rating derived
allow — alive & usable · generative ● · V n/a
Cluster mid-solo · distinctiveness 0.217 (typical). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.
🔏 Signed receipt rr_cbec1b65afa0f9fc2002d909 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
History observed
Every probe we made, oldest → newest (4 shown, 2026-08-16 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.
changelog (2 events)
| date | type | what changed |
|---|---|---|
| 2026-08-30 | outcome | ok_tools (was auth_required) |
| 2026-08-16 | outcome | first probe: auth_required |
What kind of tools these are derived
Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| generative | 9 | creates content | no answer key exists; disclosure + stability checks, never truth verdicts |
| action | 5 | changes the world | no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions |
Tools last seen observed
Harness readiness observed
Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.
| legibility check | tools passing | ok |
|---|---|---|
| name is clear & specific | 14/14 | ✓ |
| has a description | 14/14 | ✓ |
| description is substantive | 14/14 | ✓ |
| parameters are typed | 14/14 | ✓ |
| parameters are described | 5/14 | 5/14 |
14 of 14 tools graded · 14 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.
Truth checks observed
Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.
Protocol conformance observed
Capabilities: tools
Drift observed
No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-09-06T06:15:49Z | ok_tools | 200 | 199 | 2025-06-18 |
| 2026-08-30T06:15:25Z | ok_tools | 200 | 177 | 2025-06-18 |
| 2026-08-23T06:13:13Z | auth_required | 401 | 109 | |
| 2026-08-16T06:12:59Z | auth_required | 401 | 141 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/io.github.bytevirts/viewmax)
Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.
Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →