io.github.tia-forge/plc-cloud-sim
PLC Cloud Sim — LAD/SCL simulation over MCP
Is the PLC Cloud Sim MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-27.
Cloud PLC simulator: validate and step-run LAD/SCL programs, run scenarios, return PASS/FAIL.
needs auth probed 2026-11-14 · unchanged since 2026-10-27 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Unauthorized: missing or invalid API key"}}- Endpoint
- https://tia.hubwiz.com/sim/mcp (streamable-http)
- Host
- tia.hubwiz.com
- Getting access
- OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent. The publisher's guide to getting access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/tia-forge/plc-cloud-sim
- Website
- https://tia.hubwiz.com/sim
- Registry
- active, updated 2026-10-24 · registry entry
Compare this server with others.
More servers
Other registry entries on tia.hubwiz.com.
- LAD Render Cloud — SimaticML ladder diagrams over MCP io.github.tia-forge/lad-render-cloud · needs auth
- LadDoc Cloud — LadDoc to SimaticML over MCP io.github.tia-forge/laddoc-cloud · needs auth
- TIA Portal Docs — Siemens PLC programming docs over MCP io.github.tia-forge/tia-portal-docs · needs auth
Servers that mention forge.
- PartForge ai.partforge/partforge · needs auth
- SellerForge for Amazon Sellers ai.sellerforge/sellerforge · needs auth
- ScoreIA La Forge ai.scoreia/forge · alive
- app.agendaforge/agendaforge · alive
- app.agendaforge/docs · alive
- StructForge app.askqa/structforge · alive
- Eigma app.eigma/eigma · needs auth
- Forge Engine app.forgeengine/forge · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.