Discover a machine's data item structure and read a real-time snapshot using an MTConnect agent's probe and current requests
domain: docs.mtconnect.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Issue GET http://{agent}:{port}/probe (no query parameters allowed) to retrieve the MTConnectDevices document describing devices and data items
Parse the returned XML (or JSON if the agent supports Accept: application/json) to map data item IDs, types, and categories per device
Issue GET http://{agent}:{port}/current to retrieve an MTConnectStreams snapshot of the most recent value for every data item
Optionally scope the request with an XPath query parameter to limit which data items are returned
Cache the device/data-item structure from probe since it changes infrequently, and poll /current on an interval for dashboarding
Known gotchas
A probe request with any parameters supplied must have them ignored by the agent — don't rely on filtering probe itself
current always returns the last known value for a data item even if it has aged out of the agent's circular buffer, so a fresh value is not guaranteed to mean the machine is currently reporting
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?