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.

Vibresia

REMOTE · VIBRESIA.COM

Music visualiser (visualizer): write live GLSL music visualisations, shared as links that play.

Available components

69 Trust /100

Last scanned (49 minutes ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 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 Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2276 tokens (~284/item across 8 items; 8 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 4 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 1.0.0 → 1.1.0 functional
  • 3 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 68

    First indexed and scored.

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 5 Nov 2026 · Probed https://vibresia.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vibresia.com CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 6341e71bd859afdee2d76bfce1e021610ce
SANs: *.vibresia.com, vibresia.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vibresia.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
vibresia.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://vibresia.com/mcp Verified 200
http (plaintext) http://vibresia.com/mcp HTTPS enforced 301 https://vibresia.com/mcp
MCP tools · 8 exposed · ~775 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
create_vibescape ~284

Use this when somebody wants a music visualiser or music visualisation (visualizer, visualization, musicviz, audio-reactive visuals): it writes a GLSL vibescape and returns a live link to it. The link draws and animates the vibescape in a browser, so it works for anybody who opens it, with or without the app. The vibescape is not in the public gallery until `share_vibescape` is called on it. Call `vibescape_reference` first for the uniforms and helpers the language has — a vibescape that ignores the music will look like a still image, and there is a linter that says so.

NameTypeReqDescription
authorstring–Who to credit it to. Leave it empty and it is credited to Minith Labs.
codestringyesThe vibescape: a GLSL function `vec3 render(vec2 p, float t)`. `p` is the position across the screen, centred on 0,0, and `t` is time in seconds. Return the colour as three numbers from 0 to 1. Read…
namestringyesWhat to call it. A few words that say what the picture looks like.

No output schema declared.

No examples provided.

get_app ~49

Use this when somebody wants the real thing: the app listens to the system audio directly, with no browser, and updates itself. It gives the download link and the one-line install command for macOS.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_palette ~83

Use this to find out how a vibescape's colours are graded. Vibresia puts every vibescape through one of five palettes, so bright colours come out muted unless the shader accounts for it.

NameTypeReqDescription
namestring–Which palette — NEON, EMBER, TOXIC, ABYSS or MONO. Leave it out to get all of them.

No output schema declared.

No examples provided.

get_vibescape ~56

Use this to read somebody's vibescape, so it can be adapted or understood. Needs the id — the last part of the link.

NameTypeReqDescription
idstringyesThe share's id — the last part of the link.

No output schema declared.

No examples provided.

lint_vibescape ~82

Use this after writing a vibescape, before sharing it. It reads the code and says what would make it look wrong — most often that it never reads the music, so the picture is the same in silence as at full volume. Cheap to call and it catches most of what goes wrong.

NameTypeReqDescription
codestringyesThe vibescape's GLSL.

No output schema declared.

No examples provided.

list_vibescapes ~59

Use this when somebody wants to see music visualisations other people have made, or wants something to look at before writing their own. Returns the public gallery: each vibescape's name, who made it, and a link that plays it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

share_vibescape ~111

Use this when a vibescape should be listed in the public gallery, where anybody can find it at vibresia.com/vibescapes. A vibescape is created unlisted; this is the separate act of putting it in front of people. The name and the author go with it, so make sure they are right before calling this.

NameTypeReqDescription
idstringyesThe share's id — the last part of the link, six characters. It is what `create_vibescape` returns.

No output schema declared.

No examples provided.

vibescape_reference ~51

Use this before writing a vibescape: it lists every uniform the music drives and every helper the language has, with what each is for. Writing a vibescape without it usually takes two attempts instead of one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Vibresia MCP server?

Vibresia is a hosted endpoint at https://vibresia.com/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 · vibresia.com

# add to Claude Code
claude mcp add --transport http com-vibresia-music-visualizer 'https://vibresia.com/mcp'
Common questions

What is the Vibresia MCP server?

Vibresia is an MCP server listed in the public MCP registry as com.vibresia/music-visualizer. Music visualiser (visualizer): write live GLSL music visualisations, shared as links that play. This page covers its hosted endpoint (https://vibresia.com/mcp).

Is the Vibresia MCP server safe to use?

Vibresia scores 69 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 Vibresia MCP server expose?

Vibresia exposes 8 tools: create_vibescape, share_vibescape, list_vibescapes, get_vibescape, lint_vibescape, and 3 more. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.

Does the Vibresia MCP server require authentication?

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

Is the Vibresia MCP server still maintained?

Vibresia 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.