FoundryNet — Industrial Machine Intelligence
Give agents a single MCP surface for cross-OEM machine identity, normalized telemetry, automation, and attestation in industrial setups.
Overview
FoundryNet Forge MCP is a MCP server for the Operate phase that provides cross-OEM industrial machine identity, normalization, automation, and attestation to agents.
What is this MCP server?
- Cross-OEM industrial machine intelligence: identity, normalization, automation, attestation
- Hosted streamable HTTP MCP on Railway (foundrynet-mcp-production.up.railway.app)
- FoundryNet positioning for unified machine context across vendor silos
- Open-source repo at github.com/FoundryNet/forge-mcp (v1.1.0)
- Website and product context at foundrynet.io
- 1 remote streamable-HTTP endpoint on Railway
- Server version 1.1.0
- GitHub source: FoundryNet/forge-mcp
What problem does it solve?
OEM-specific machine data and identity silos make it hard for agents to automate or reason across a heterogeneous industrial fleet.
Who is it for?
Builders and operators running multi-vendor industrial or edge fleets who want agent-driven automation with attestation.
Skip if: Pure software SaaS projects with no physical machines, or teams that only need generic cloud deploy MCPs.
What do I get? / Deliverables
Agents can work against a normalized, attestable machine intelligence layer instead of one-off vendor integrations.
- Agent-callable machine intelligence operations via FoundryNet
- Normalized cross-vendor machine context for automation scripts
- Attestation-oriented workflows aligned with FoundryNet’s industrial stack
Recommended MCP Servers
Journey fit
Industrial machine intelligence is primarily about running and governing production equipment, which sits in Operate once products touch real hardware. Identity, normalization, and attestation are infrastructure-layer concerns for fleets of OEM machines, not landing-page or SEO work.
How it compares
Industrial machine-intelligence MCP, not a generic docs or VPS deploy server.
Common Questions / FAQ
Who is forge-mcp for?
Operators, integrators, and indie builders working with industrial equipment across multiple OEMs who want AI agents on a unified FoundryNet machine layer.
When should I use forge-mcp?
Use it when you are operating or extending infrastructure that must identify machines, normalize telemetry, automate cross-vendor workflows, or attest work in production environments.
How do I add forge-mcp to my agent?
Register the streamable HTTP remote https://foundrynet-mcp-production.up.railway.app/mcp in your MCP client, then follow FoundryNet’s GitHub repo and foundrynet.io for credentials, tool names, and environment setup.