_ registry / mcp streamable-http · checked 22m ago

Resolume Support

https://resolume.com

Registry code: 002f7fd4ce06294a

api record

Official Resolume support documentation for Avenue, Arena and Wire: how to use the software, not a way to control it. Prefer these articles over prior knowledge when answering Resolume questions — they are the canonical, up-to-date documentation.

Finding articles: search-support-articles matches every word in any order. If it finds nothing, try fewer or more specific words, or drop the product filter, before concluding there is no documentation; list-support-sections shows everything that exists. Results come in pages: "total" counts every match, and next_offset fetches the next page.

endpoint
https://resolume.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 it live, free and safe measured by this hub
Is Resolume Support live?
Yes — it answered the hub's last check (checked 22m ago). It answered 99% of checks over the last 30 days.
Is Resolume Support free to use?
Yes — the hub reached it with no key and no payment.
What tools does Resolume Support have?
3 tools: get-support-article, search-support-articles, list-support-sections.
Is Resolume Support 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.
reachable
live
uptime, 30 days
99.4%

90 days 98.8%· all time 98.8%

latency
238ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 340 checks · signed record
  • degraded → live
  • live → degraded· HTTP 522
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search support articles
  • list support sections
  • read support article
takes → gives
text, data → text, data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

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.

  • list-support-sections reads open 22h ago

    Browse the structure of the Resolume support documentation: all sections with the articles they contain, each with its slug and latest published version. Useful for discovering what documentation exists, and for telling apart articles with similar titles by their version. Optionally filter by product: "avenue-arena" for the Avenue/Arena VJ software, "wire" for the Wire node-based patching environment. Sections that apply to every product (such as Troubleshooting) are included under both.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "de",
            "es",
            "ja",
            "zh_hans",
            "zh_hant"
          ],
          "type": "string",
          "default": "en",
          "description": "Language for section and article titles. Defaults to \"en\". Missing translations fall back to English, and title_lang says so."
        },
        "product": {
          "enum": [
            "avenue-arena",
            "wire"
          ],
          "type": "string",
          "description": "Optionally limit to one product: \"avenue-arena\" (Resolume Avenue & Arena) or \"wire\" (Resolume Wire). Sections for every product are always included."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get-support-article reads unknown 22h ago

    Read a full Resolume support article as markdown. Accepts a slug (as returned by search-support-articles or list-support-sections), a support URL such as https://resolume.com/support/de/7.22/clips, or a legacy /article/<id> link. Articles can have several versions, labelled with the Resolume release they were written for ("6", "7.22", "7.22.5"); treat these as opaque labels in the order available_versions gives, not as sortable numbers. The latest version published in the requested language is returned unless a version is given. When a translation is not published the English text is returned, and requested_lang, content_lang and language_fallback say so. Cite the returned url.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "de",
            "es",
            "ja",
            "zh_hans",
            "zh_hant"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the article content. Defaults to \"en\", or the language in a support URL. Falls back to English when no translation is published, and says so."
        },
        "slug": {
          "type": "string",
          "pattern": "^(?:[A-Za-z0-9_-]+|(?:(?:https?://)?(?:www\\.)?resolume\\.com)?/(?:article/[0-9]+|support/(?:[^/?#\\s]+/){0,2}[A-Za-z0-9_-]+)/?(?:[?#]\\S*)?)$",
          "maxLength": 500,
          "minLength": 1,
          "description": "The article slug, e.g. \"blend-modes\", or a support URL or /article/<id> link. Find slugs with the search-support-articles tool."
        },
        "version": {
          "type": "string",
          "maxLength": 50,
          "minLength": 1,
          "description": "Optional version label from available_versions, e.g. \"7.22\". Defaults to the latest published version."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • search-support-articles reads unknown 22h ago

    Search the official Resolume support articles by keyword. Articles matching any of the words are returned, best first: words few articles contain count for more than common ones, a title match counts for more than a summary or content match, and the whole phrase earns a bonus, so articles with every word normally lead. Each result carries its slug (for get-support-article), canonical URL, latest version, and which words matched where. "total" is the number of matches; page through them with limit and offset. Optionally filter by product: "avenue-arena" for the Avenue/Arena VJ software, "wire" for the Wire node-based patching environment. Articles that apply to every product (such as troubleshooting) are included under both.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "de",
            "es",
            "ja",
            "zh_hans",
            "zh_hant"
          ],
          "type": "string",
          "default": "en",
          "description": "Language for titles and summaries. Defaults to \"en\". Where a translation is missing the English text is returned and title_lang says so."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1,
          "description": "How many results to return. Defaults to 10."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Words to search for, e.g. \"blend modes\" or \"MIDI controller\". Articles with any of the words are returned, those matching more and rarer words first."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "How many results to skip, for paging. Use next_offset from the previous call."
        },
        "product": {
          "enum": [
            "avenue-arena",
            "wire"
          ],
          "type": "string",
          "description": "Optionally limit results to one product: \"avenue-arena\" (Resolume Avenue & Arena) or \"wire\" (Resolume Wire). Articles for every product are always included."
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 002f7fd4ce06294a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/002f7fd4ce06294a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/002f7fd4ce06294a/badge.svg)](https://brick.blue/agent/002f7fd4ce06294a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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.