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

gdtf-lights-dmx-to-gdtf

https://gdtf-lights.com

Registry code: 39873b4e5ede7e64

api record

Identifies lighting fixtures by their DMX channel layout in the GDTF Stage Studio library (https://gdtf-lights.com) of 10500+ fixtures with GDTF profiles, run by SOH Sound & Lights s.r.o., Prague. Give match_dmx_channels the channel names in DMX order from address 1 (from a manual, a console, a fixture-profile TXT or a photo the person describes). It returns the best matching fixtures with score 0-100 and the matched DMX mode, with links to the fixture page and the .gdtf file. With confidence low or same_score_count above 1 say the result is uncertain and ask for the manufacturer or DMX…

endpoint
https://gdtf-lights.com/mcp/dmx-to-gdtf
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 gdtf-lights-dmx-to-gdtf live?
Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
Is gdtf-lights-dmx-to-gdtf free to use?
Not measured yet.
What tools does gdtf-lights-dmx-to-gdtf have?
1 tool: match_dmx_channels.
Is gdtf-lights-dmx-to-gdtf 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
100%

90 days 100%· all time 100%

latency
438ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 1 tools
1 never probed 0 of 1 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.

  • match_dmx_channels unknown 32m ago

    Finds the fixtures whose GDTF profile matches a DMX channel list and the matched DMX mode: channel names in DMX order from address 1 (English, Czech, German or Spanish; abbreviations, synonyms and typos are understood), as in a manual, on a console or in a fixture-profile TXT. Give channels (a list) or text (a pasted list, or a TXT with one or more modes; rows such as "Shutter;0;Closed;32;Open" add DMX values as a tie-breaker). Returns up to limit fixtures with score 0-100, the matched GDTF mode (mode.name and mode.channels), links to the fixture page (url) and the .gdtf file (gdtf_url), confidence and same_score_count (several fixtures with the same layout: ask for the manufacturer or DMX values). Same search as https://gdtf-lights.com/dmx-to-gdtf. Limit per IP: 20000 searches a day and 300 a minute, shared with the JSON API of that page; 500 a minute and 10000 an hour for all API and MCP clients together.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "text": {
          "type": "string",
          "maxLength": 100000,
          "description": "Instead of channels: a pasted channel list (one per line, numbered or comma-separated) or a fixture-profile TXT (***mode:N***, --- Mode: ---, ##Name;N##)"
        },
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 10,
          "minimum": 1
        },
        "channels": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 120
          },
          "maxItems": 512,
          "minItems": 1,
          "description": "Channel names in DMX order, address 1 first, e.g. [\"Pan\", \"Pan fine\", \"Tilt\", \"Tilt fine\", \"Dimmer\", \"Shutter\", \"Color wheel\", \"Gobo\"]; use \"Empty\" for an unused address"
        },
        "include_diff": {
          "type": "boolean",
          "default": false,
          "description": "Add for each match the DMX addresses that differ (your channel vs the fixture channel)"
        },
        "manufacturer": {
          "type": "string",
          "maxLength": 100,
          "description": "Only fixtures of this manufacturer; part of the name is enough, e.g. \"Robe\""
        }
      },
      "additionalProperties": false
    }
    arguments 37 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 39873b4e5ede7e64.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/39873b4e5ede7e64/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/39873b4e5ede7e64/badge.svg)](https://brick.blue/agent/39873b4e5ede7e64?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
50%

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.