● Paid MCP server · v0.1.0 · 1 USDC per call on Base

Industrial Migration Exception Resolver

An evidence-backed MCP tool for investigating migration paths for obsolete industrial components.

MCP endpoint
https://migration-exception-mcp-mainnet.awaw-999-iw.workers.dev/mcp

What it returns

Given a legacy industrial part number, the resolver can return migration candidates, compatibility constraints, evidence references, missing engineering context, and explicit uncertainty.

It does not invent compatibility and does not provide engineering approval.

Validated cases

Siemens EM 253
6ES7253-1AA22-0XA0

Migration information involving S7-1200 PTO, Motion Control technology objects, conditional V90 reuse, and engineering review requirements.
Siemens EM 231
6ES7231-0HC22-0XA0

Ranked functional migration candidates including 6ES7231-5ND32-0XB0 and 6ES7234-4HE32-0XB0, with signal, scaling, wiring, and application-context conditions preserved.

Unknown parts stay unknown

When no validated migration record exists, the resolver returns DISCOVERY_REQUIRED instead of fabricating an answer.

For agents

Tool: resolve_migration_exception

Paid x402 infrastructure. Calls cost 1 USDC on Base. Current validated coverage is intentionally narrow.

Paid access

1 USDC per resolver call
Payment is handled through x402 on Base.

MCP endpoint
https://migration-exception-mcp-mainnet.awaw-999-iw.workers.dev/mcp

Connect this endpoint to an x402-compatible MCP client or agent. Discovery and tool metadata are available without payment. Payment is required when resolve_migration_exception is called.

What happens on a paid call

1. Submit a legacy part number
The resolver investigates the validated migration knowledge available for that component.
2. Receive structured migration evidence
Results can include ranked migration candidates, compatibility conditions, evidence references, missing engineering context, and explicit uncertainty.
3. Keep unresolved engineering questions visible
The resolver does not invent compatibility and does not turn a conditional candidate into engineering approval.

How to use the result

A migration candidate is a starting point, not engineering approval.

CONDITIONAL means the candidate is evidence-backed but still depends on the listed compatibility conditions.

REQUIRED means human engineering review is still needed before implementation.

Check remaining_context, candidate conditions, and evidence before treating a result as implementation-ready.

Machine-readable by design
Successful MCP calls return both structured content and the complete resolver result, together with the x402 payment response.