_ registry / mcp streamable-http · checked 1h ago

plcgateway-support

https://plcgateway.com

Registry code: 5a09e15f2b97e258

api record

Official support server of PLCGateway (plcgateway.com), industrial software with AI built in: Connect (PLC/CNC connectivity and OPC UA server), SCADA (Connect + screens, alarms, history, reports, OEE), Embedded (SCADA + operator panel on the device), with the Quality & Maintenance and Energy management modules. Answers come from the website's own content. Use product_info to explain products, modules and topics, device_support to check a PLC, CNC or protocol, price_quote for prices (EUR, excl. VAT), search_docs for anything else, and request_demo to send the team a demo or offer request after…

endpoint
https://plcgateway.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 plcgateway-support live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is plcgateway-support free to use?
Yes — the hub reached it with no key and no payment.
What tools does plcgateway-support have?
5 tools: search_docs, request_demo, device_support, price_quote, product_info.
Is plcgateway-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
100%

90 days 100%· all time 100%

latency
308ms

last good check

priced tools
0

of 5 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 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.

  • search_docs unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
    },
    "language": {
      "enum": [
        "en",
        "de",
        "es",
        "fr",
        "it",
        "pt",
        "ro",
        "bg",
        "ru",
        "tr",
        "ar"
      ],
      "type": "string",
      "default": "en",
      "description": "Answer language: the user's language if available."
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • request_demo unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "user_confirmed"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1
    },
    "email": {
      "type": "string",
      "format": "email",
      "maxLength": 160
    },
    "phone": {
      "type": "string",
      "maxLength": 40
    },
    "company": {
      "type": "string",
      "maxLength": 160
    },
    "message": {
      "type": "string",
      "maxLength": 2000,
      "description": "Machines, controllers, number of computers, goals, preferred time for a call."
    },
    "product": {
      "enum": [
        "connect",
        "scada",
        "embedded",
        "enterprise",
        "not_sure"
      ],
      "type": "string",
      "default": "not_sure"
    },
    "language": {
      "enum": [
        "en",
        "de",
        "es",
        "fr",
        "it",
        "pt",
        "ro",
        "bg",
        "ru",
        "tr",
        "ar"
      ],
      "type": "string",
      "default": "en",
      "description": "Answer language: the user's language if available."
    },
    "user_confirmed": {
      "type": "boolean",
      "description": "true only after the user has seen these details and agreed to send them."
    }
  },
  "additionalProperties": false
}
    arguments 67 lines
  • device_support unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Controller model or family, brand, protocol or driver name."
    },
    "language": {
      "enum": [
        "en",
        "de",
        "es",
        "fr",
        "it",
        "pt",
        "ro",
        "bg",
        "ru",
        "tr",
        "ar"
      ],
      "type": "string",
      "default": "en",
      "description": "Answer language: the user's language if available."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • price_quote unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "product"
  ],
  "properties": {
    "modules": {
      "type": "array",
      "items": {
        "enum": [
          "quality_maintenance",
          "energy"
        ],
        "type": "string"
      },
      "default": [],
      "uniqueItems": true
    },
    "product": {
      "enum": [
        "connect",
        "scada",
        "embedded",
        "enterprise"
      ],
      "type": "string"
    },
    "language": {
      "enum": [
        "en",
        "de",
        "es",
        "fr",
        "it",
        "pt",
        "ro",
        "bg",
        "ru",
        "tr",
        "ar"
      ],
      "type": "string",
      "default": "en",
      "description": "Answer language: the user's language if available."
    },
    "computers": {
      "type": "integer",
      "default": 1,
      "maximum": 1000,
      "minimum": 1,
      "description": "Number of computers (one licence each)."
    },
    "maintenance_years": {
      "type": "integer",
      "default": 0,
      "maximum": 10,
      "minimum": 0,
      "description": "Years of updates and support bought after the included first year."
    }
  },
  "additionalProperties": false
}
    arguments 62 lines
  • product_info unknown 1h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "enum": [
        "overview",
        "connect",
        "scada",
        "embedded",
        "quality_maintenance",
        "energy",
        "oee_production",
        "ai_mcp",
        "integrations",
        "protocols",
        "pricing",
        "plc_gateway_guide",
        "kepserverex_migration",
        "contact",
        "references"
      ],
      "type": "string"
    },
    "language": {
      "enum": [
        "en",
        "de",
        "es",
        "fr",
        "it",
        "pt",
        "ro",
        "bg",
        "ru",
        "tr",
        "ar"
      ],
      "type": "string",
      "default": "en",
      "description": "Answer language: the user's language if available."
    }
  },
  "additionalProperties": false
}
    arguments 47 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 5a09e15f2b97e258.

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

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.