The problem is shipping an ICIS/eCorp deployment Config XML that the C# ConfigFileManager would reject — after you are already in a window. MCV validates that XML against the embedded PRM MSI XSD (Configuration → Deployment → Jira/File). Paste, Validate, get line-numbered errors, warnings split from fatals, and a parsed summary of every Jira and File element plus BackupFolder — even when validation fails. Load Example fills a valid sample. Ctrl/Cmd+Enter runs validate. XML parse is hardened: no entity resolution, no network, huge_tree off. MCP tool mcv_validate_xml is declared. Public /mcv/; the tool is /mcv/app behind login.
MCV is for deployment engineers and release managers. It is not a generic XML pretty-printer.
CSS mock — not a screenshot of Visual Studio or ConfigFileManager.
Errors are schema violations with lines. Warnings are non-fatal XSD WARNING messages.
Parse-on-failure is the feature. BackupFolder from Deployment is shown.
/mcv/ and health are public. /mcv/app and POST /mcv/api/validate require login.
Safe XML parsing: entity resolution disabled, no network access, billion-laughs hardening. This is a validator, not an XXE gadget.
MCV will not execute a production deployment, talk to Jira, or fetch files from SourceLocation. It will not invent a second schema. If the C# tool and this XSD drift, that is a schema problem — do not hide it with a prettier table.
Release managers verifying ICIS/eCorp deployment documents before a window. MCP consumers calling mcv_validate_xml. How you verify: Load Example is valid; break a File element and see a line error; summary still lists parsed Jira rows; unauthenticated POST redirects.
Embedded PRM MSI XSD. JSON API. MCP declaration.
Login for /mcv/app. This page does not accept uploads.
Open MCVRequires a MelTuc account. Create one free.
Validate deployment Config XML files against the PRM MSI configuration schema. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.