# DMX to GDTF (remote · gdtf-lights.com)

Identify a lighting fixture and its DMX mode from a DMX channel list (10,500+ GDTF profiles).

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gdtf-lights.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-gdtf-lights-dmx-to-gdtf/mcp-dmx-to-gdtf.md), [page](https://verifymcp.io/servers/com-gdtf-lights-dmx-to-gdtf/mcp-dmx-to-gdtf)

## Channel facts

- Endpoint: `https://gdtf-lights.com/mcp/dmx-to-gdtf`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 668 tokens (~668/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the DMX to GDTF MCP server?

DMX to GDTF is a hosted endpoint at https://gdtf-lights.com/mcp/dmx-to-gdtf, 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.

### Claude

```bash
claude mcp add --transport http com-gdtf-lights-dmx-to-gdtf 'https://gdtf-lights.com/mcp/dmx-to-gdtf'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gdtf-lights-dmx-to-gdtf": {
      "url": "https://gdtf-lights.com/mcp/dmx-to-gdtf"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gdtf-lights-dmx-to-gdtf": {
      "type": "http",
      "url": "https://gdtf-lights.com/mcp/dmx-to-gdtf"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gdtf-lights-dmx-to-gdtf]
url = "https://gdtf-lights.com/mcp/dmx-to-gdtf"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gdtf-lights-dmx-to-gdtf": {
      "type": "remote",
      "url": "https://gdtf-lights.com/mcp/dmx-to-gdtf",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gdtf-lights-dmx-to-gdtf --url 'https://gdtf-lights.com/mcp/dmx-to-gdtf' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gdtf-lights-dmx-to-gdtf:
    url: "https://gdtf-lights.com/mcp/dmx-to-gdtf"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gdtf-lights-dmx-to-gdtf": {
      "Transport": "http",
      "Url": "https://gdtf-lights.com/mcp/dmx-to-gdtf"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gdtf-lights-dmx-to-gdtf -t streamable-http -u 'https://gdtf-lights.com/mcp/dmx-to-gdtf'
```

### Other

```json
{
  "mcpServers": {
    "com-gdtf-lights-dmx-to-gdtf": {
      "type": "http",
      "url": "https://gdtf-lights.com/mcp/dmx-to-gdtf"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 68, +1)

- [functional improvement] Tool coverage: 80% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.5.0 → 1.5.1
- [cosmetic] “match_dmx_channels” reworded the description of “limit”

## MCP tools (1)

### `match_dmx_channels` (~434 tokens)

Identify fixture by DMX channels

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.

Input parameters:

- `channels` (array): 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` (boolean): Add for each match the DMX addresses that differ (your channel vs the fixture channel)
- `limit` (integer): Maximum number of fixtures to return, best score first (1-10, default 5)
- `manufacturer` (string): Only fixtures of this manufacturer; part of the name is enough, e.g. "Robe"
- `text` (string): Instead of channels: a pasted channel list (one per line, numbered or comma-separated) or a fixture-profile TXT (***mode:N***, --- Mode: ---, ##Name;N##)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-gdtf-lights-dmx-to-gdtf/mcp-dmx-to-gdtf#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68
- 2026-11-07: 67

## Common questions

### What is the DMX to GDTF MCP server?

DMX to GDTF is an MCP server listed in the public MCP registry as com.gdtf-lights/dmx-to-gdtf. Identify a lighting fixture and its DMX mode from a DMX channel list (10,500+ GDTF profiles). This page covers its hosted endpoint (https://gdtf-lights.com/mcp/dmx-to-gdtf).

### Is the DMX to GDTF MCP server safe to use?

DMX to GDTF scores 75 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 DMX to GDTF MCP server expose?

DMX to GDTF exposes 1 tool: match_dmx_channels. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

### Does the DMX to GDTF MCP server require authentication?

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

### Is the DMX to GDTF MCP server still maintained?

DMX to GDTF is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DMX to GDTF MCP server?

VerifyMCP ran 13 checks on DMX to GDTF, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://gdtf-lights.com/mcp/dmx-to-gdtf
- Website: https://gdtf-lights.com/dmx-to-gdtf
- Changelog RSS feed: https://verifymcp.io/servers/com-gdtf-lights-dmx-to-gdtf/mcp-dmx-to-gdtf.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gdtf-lights-dmx-to-gdtf/mcp-dmx-to-gdtf/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-gdtf-lights-dmx-to-gdtf/mcp-dmx-to-gdtf.json
- HTML version of this page: https://verifymcp.io/servers/com-gdtf-lights-dmx-to-gdtf/mcp-dmx-to-gdtf
