vibresia

endpoint

https://vibresia.com/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is vibresia live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is vibresia free to use?

Yes — the hub reached it with no key and no payment.

What tools does vibresia have?

8 tools: create_vibescape, share_vibescape, get_vibescape, lint_vibescape, vibescape_reference, get_app, get_palette, list_vibescapes.

Is vibresia safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_app open 1h ago

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_palette open 1h ago

  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.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "Which palette — NEON, EMBER, TOXIC, ABYSS or MONO. Leave it out to get all of them."
      }
    }
  }

  arguments 9 lines copy
• list_vibescapes open 1h ago

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• create_vibescape unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "code",
      "name"
    ],
    "properties": {
      "code": {
        "type": "string",
        "description": "The 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 the music through the uniforms — uBass, uLevelSmooth, uBeatStrength, uScroll — or the picture will not move with the sound."
      },
      "name": {
        "type": "string",
        "description": "What to call it. A few words that say what the picture looks like."
      },
      "author": {
        "type": "string",
        "description": "Who to credit it to. Leave it empty and it is credited to Minith Labs."
      }
    }
  }

  arguments 21 lines copy
• share_vibescape unknown never probed

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The share's id — the last part of the link, six characters. It is what `create_vibescape` returns."
      }
    }
  }

  arguments 12 lines copy
• get_vibescape unknown never probed

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

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The share's id — the last part of the link."
      }
    }
  }

  arguments 12 lines copy
• lint_vibescape unknown never probed

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "description": "The vibescape's GLSL."
      }
    }
  }

  arguments 12 lines copy
• vibescape_reference unknown never probed

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.