Skip to content

PLCGateway support MCP server

com.plcgateway/supportplcgateway.comstreamable-httpv1.0.0Scanned

PLCGateway products, modules, PLC/CNC driver support, prices and demo requests, in 11 languages.

5 tools: 1 do something that can't be undone, 2 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 PLCGateway support MCP server can do

The PLCGateway support MCP server is published by plcgateway.com, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_demo) and create or change data (2 tools: device_support and price_quote), but cannot delete data. 2 tools only read.

1 tool reads private data (search_docs); 2 tools bring in text other people can write (search_docs and request_demo); 1 tool can send data out of your system (request_demo). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way 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 18, 2026, version 1.0.0.

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.

5 tools

Can't be undone 1Claude Code: ask
  • request_demoSends a demo, trial or offer request to the PLCGateway team by e-mail; they answer the user directly.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "request_demo" says "request": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Sends a demo, trial or offer request to the PLCGateway team by e-mail; they answer the user directly. Ask the user for their name and e-mail address; company, phone, the product they are interested in and a short description of their machines and goals are optional but help. Never invent, guess or reuse contact details the user did not give for this request. Before calling, show the user exactly what will be sent and ask for permission; set user_confirmed to true only after they explicitly agreed. Their details are used only to answer the request (privacy notice: https://plcgateway.com/privacy).

    Annotations the server declares

    • title: Send a demo or offer request
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • device_supportChecks whether a PLC, CNC, controller family, model, brand or protocol is supported and returns its page: which driver, connection settings, address syntax with examples, what can …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks whether a PLC, CNC, controller family, model, brand or protocol is supported and returns its page: which driver, connection settings, address syntax with examples, what can be read, tips and FAQ. Examples: "S7-1200", "CompactLogix", "MELSEC iQ-R", "FANUC 0i-F", "Modbus RTU", "IEC 104", "BACnet". Without a match it lists the supported protocols.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Check controller or protocol support
  • price_quoteCalculates the list price of PLCGateway licences in EUR, excluding VAT: product, number of computers, optional modules (SCADA and Embedded only) and optional years of updates and s…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Calculates the list price of PLCGateway licences in EUR, excluding VAT: product, number of computers, optional modules (SCADA and Embedded only) and optional years of updates and support after the first year (included). Licences are perpetual, one per computer, with every driver and no device or tag limit. Embedded and Enterprise are priced on request: offer request_demo then.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Price for a setup
Only reads 2Show 2 read-only tools
  • product_infoExplains what a PLCGateway product, module or topic is for, who it is for, what it includes and how it works, from the official website.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    Explains what a PLCGateway product, module or topic is for, who it is for, what it includes and how it works, from the official website. Topics: overview (compare Connect, SCADA and Embedded, what each includes, platforms), connect (machine connectivity and OPC UA server), scada (screens, alarms, history, reports, OEE), embedded (operator panel on the device's own display, ARM panels, panel PCs), quality_maintenance (module: SPC control charts, maintenance plans, CMMS), energy (module: ISO 50001 energy management), oee_production (production model, OEE, batches, downtime), ai_mcp (the MCP server built into every product and what AI assistants can do with it), integrations (OPC UA, MQTT, Modbus TCP server, REST API), protocols (all drivers and supported controllers), pricing (prices, licences, trial, maintenance), plc_gateway_guide (what a PLC gateway is), kepserverex_migration (moving tags from KEPServerEX), contact, references (customers and installations: in use at factories in many countries, names not published).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Product and topic information
  • search_docsSearches all pages of plcgateway.com (products, modules, protocols, controllers, guides) and returns the best matching pages with URL and summary.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Searches all pages of plcgateway.com (products, modules, protocols, controllers, guides) and returns the best matching pages with URL and summary. Follow up with product_info or device_support for the full text.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Search the website

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.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__support__request_demo"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:22 UTC, unchanged since Nov 5, 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
3
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://plcgateway.com/mcp: tools/list returned 5 tools to an anonymous client, including request_demo (irreversible), device_support (write), price_quote (write)

    What this check looks for

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.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http support https://plcgateway.com/mcp
claude mcp add --transport http support https://plcgateway.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__support__product_info",
      "mcp__support__search_docs"
    ],
    "ask": [
      "mcp__support__device_support",
      "mcp__support__price_quote",
      "mcp__support__request_demo"
    ],
    "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 support. Review it before you use it.

Capability tags behind 2 rules
  • mcp__support__search_docs private-data, untrusted-input
  • mcp__support__request_demo untrusted-input, outbound

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.plcgateway/support/verify?hash=dbceae31b68af2740a2366751adfab670aebe1948942eeefd3271dc2666fbfcc" | jq -e '.changed == false'

Pinned hash dbceae31b68a, from Nov 18, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.plcgateway/support/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.plcgateway/support
[![Anlyon Radar](https://radar.anlyon.com/badge/com.plcgateway/support.svg)](https://radar.anlyon.com/servers/com.plcgateway/support)

Source: MCP Registry. Synced Nov 4, 2026, 10:17 UTC.

PLCGateway support MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PLCGateway support MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PLCGateway support MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PLCGateway support MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: request_demo.

What tools does the PLCGateway support MCP server have?

5 tools: 1 irreversible, 2 write, 2 read. request_demo, device_support, price_quote, product_info and search_docs.

Does the PLCGateway support MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PLCGateway support MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_demo.

Has the PLCGateway support MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.