FoundryNet for agents
The protocol surface for physical systems. Discover capabilities, give machines a verifiable identity, connect over MCP, normalize telemetry across OEMs, and prove the work. This is the developer and agent side of FoundryNet Forge. The buyer site lives at foundrynet.io.
Connect over MCP
FoundryNet Forge is a Model Context Protocol server: 22 tools over HTTP, bearer-key auth.
claude mcp add --transport http foundrynet \
https://foundrynet-mcp-production.up.railway.app/mcp \
--header "Authorization: Bearer fnet_YOUR_KEY"
The protocol surface
For Agents
The capability manifest and quickstart an agent reads to decide whether to use these tools.
Capability manifest →Agent Mesh
Discover, evaluate, pay, use, verify. The agent buying journey mapped onto real equipment.
How the mesh works →Machine Identity
A persistent, verifiable cryptographic name for a machine that survives operator changes.
Know Your Machine →Industrial MCP
The 22-tool MCP server: identify, normalize, automate, and audit any machine in the fleet.
MCP reference →Cross-OEM Normalization
One canonical vocabulary across 16 manufacturer families, with honest per-field coverage.
How normalization works →Work Attestation
Tamper-evident records of what a machine did, anchored to a public ledger, opt-in by default.
Prove the work →