DMX to GDTF MCP server
com.gdtf-lights/dmx-to-gdtfgdtf-lights.comstreamable-httpv1.5.1Scanned
Identify a lighting fixture and its DMX mode from a DMX channel list (10,500+ GDTF profiles).
1 tool: 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DMX to GDTF MCP server can do
The DMX to GDTF MCP server is published by gdtf-lights.com, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.5.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Only reads 1Show 1 read-only tool
match_dmx_channelsFinds 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; abbreviatio…No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Identify fixture by DMX channels
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:match_dmx_channelsOnly readsinputSchema
Install
Pinned to version 1.5.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http dmx-to-gdtf https://gdtf-lights.com/mcp/dmx-to-gdtfclaude mcp add --transport http dmx-to-gdtf https://gdtf-lights.com/mcp/dmx-to-gdtfRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dmx-to-gdtf__match_dmx_channels"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dmx-to-gdtf. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.gdtf-lights/dmx-to-gdtf/verify?hash=43b68c87f843b1fb2d2cc576b8863d83c5a990edc20205d925f29a36e7668387" | jq -e '.changed == false'Pinned hash 43b68c87f843, from Nov 8, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.gdtf-lights/dmx-to-gdtf/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.gdtf-lights/dmx-to-gdtf)Source: MCP Registry. Synced Nov 8, 2026, 07:17 UTC.
DMX to GDTF MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DMX to GDTF MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the DMX to GDTF MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the DMX to GDTF MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the DMX to GDTF MCP server have?
- 1 tool: 1 read. match_dmx_channels.
Does the DMX to GDTF MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the DMX to GDTF MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DMX to GDTF MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.