Is the FoundryNet — Industrial Machine Intelligence MCP server down?

mcp-registry/io.github.foundrynet/forge-mcp · registry v1.1.0 · server reports v3.4.4

Also listed as awesome/foundrynet/forge-mcp

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
down
Last checked 2026-11-22 00:19 UTC · handshake 70ms

As of 2026-11-22 00:19 UTC, the FoundryNet — Industrial Machine Intelligence MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.

uptime (30d checks)
0%
checks observed
6
outages (90d)
0
tools
30

Cross-OEM industrial machine intelligence: identity, normalization, automation, attestation.

Point your MCP client at this streamable-http endpoint: https://foundrynet-mcp-production.up.railway.app/mcp

Agent-readiness: D (63/100)

D (63/100): 1 error(s), 3 warning(s) across 30 tool(s); ~6,622 tokens of tool definitions.
Scores higher than 1% of 27,592 MCP servers Glimind has audited.
Its tool list costs an agent ~6,622 tokens per session — more than 70% of servers.
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints15
Token cost100
Client compatibility100
Protocol100
Reliability0
Stability100

What to fix (4)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

30 of 30 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: activate_automation, calculate_oee, correct_mapping, create_automation, delete_automation and 25 more

83 parameter(s) across 28 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: activate_automation, calculate_oee, correct_mapping, create_automation, delete_automation and 23 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_automation, delete_automation

Auto-fix: 12 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 28 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.foundrynet%2Fforge-mcp/fixes

calculate_oee 1 change
{
  "name": "calculate_oee",
  "description": "Overall Equipment Effectiveness (OEE = Availability × Performance ×\nQuality) for one machine over a period, computed from telemetry the kernel\nalready collects. Returns the three-factor breakdown, a letter grade, and an\nhonest `available:false` with a reason when there isn't enough data.\n\nArgs:\n  machine_id  the machine's id (e.g. \"DEMO-FANUC-01\")\n  period      \"shift\" (default), \"day\", or \"week\"\n\nUSE WHEN: your agent needs to report how a machine is performing, locate\nwhere the losses are, or p",
  "inputSchema": {
    "type": "object",
    "required": [
      "machine_id"
    ],
    "properties": {
      "period": {
        "type": "string",
        "default": "shift"
      },
      "machine_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
create_automation 1 change
{
  "name": "create_automation",
  "description": "Let your agent wire machine telemetry to any business system in plain\nEnglish — ERP, CMMS, MES, Slack, Teams, email, Zapier, n8n — via webhooks\nalready registered as tools on the Forge service. The agent describes the\ncondition and the action; Forge parses it into a structured trigger.\n\nExamples of `instruction`:\n  \"Alert maintenance Slack when spindle load exceeds 90 percent.\"\n  \"Create a Fiix work order when coolant temperature stays above 35°C\n   for five minutes.\"\n  \"Notify the supervisor wh",
  "inputSchema": {
    "type": "object",
    "required": [
      "mint_id",
      "instruction"
    ],
    "properties": {
      "mint_id": {
        "type": "string"
      },
      "instruction": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
delete_automation 1 change
{
  "name": "delete_automation",
  "description": "Soft-deletes the trigger (recoverable for 30 days via\nrestore_automation). The trigger immediately stops evaluating against\n/v1/normalize calls and is hidden from list_automations, but the row\npersists with deleted_at set so an accidental delete can be undone.\nUse restore_automation to undo. For permanent deletion, the API\nsupports ?permanent=true.\n\nPast forge_trigger_executions rows for this trigger remain in either\ncase (audit trail).\n\nUSE WHEN: the user wants to remove an automation they no l",
  "inputSchema": {
    "type": "object",
    "required": [
      "trigger_id"
    ],
    "properties": {
      "trigger_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.foundrynet/forge-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.foundrynet/forge-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.foundrynet%2Fforge-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.foundrynet%2Fforge-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.foundrynet%2Fforge-mcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.foundrynet%2Fforge-mcp.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b3b9c389c45c5e50…, first seen 2026-10-17, included at leaf 12830 of 384,046. Version history · verify what your client received.

Working alternatives

Tools (30)

Compare: most reliable devops servers · most reliable data servers · most reliable ml servers · most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the FoundryNet — Industrial Machine Intelligence MCP server down right now?

As of 2026-11-22 00:19 UTC, the FoundryNet — Industrial Machine Intelligence MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.

How many tools does FoundryNet — Industrial Machine Intelligence MCP server provide?

FoundryNet — Industrial Machine Intelligence MCP server advertises 30 tools, including activate_automation, calculate_oee, correct_mapping, create_automation, delete_automation.

How do I install FoundryNet — Industrial Machine Intelligence MCP server?

Point your MCP client at this streamable-http endpoint: https://foundrynet-mcp-production.up.railway.app/mcp

Is the FoundryNet — Industrial Machine Intelligence MCP server safe to connect to an AI agent?

Glimind scanned all 30 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of FoundryNet — Industrial Machine Intelligence MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve