Use in your browser
Validate a hosted OCDS release or record package against its schema, declared extensions, and additional conformance checks. Comparisons rank or diff only packages with the same query-insensitive canonical package/feed identity, detected version, and package kind.
Guest includes 50 lifetime app requests. Create a free account for 100 app requests each calendar month. One allowance across every app, in your browser and your agent.One allowance across every app, in your browser and your agent. Manage usage
Guest access is available after setup. Full account linking verified by PowMCP: Claude only.
Connect this app on its own. Add other PowMCP apps whenever your agent needs another job done.
Open the apps workspace
Choose your agent. Each button opens a new tab with only this app's endpoint ready to add.
ClaudeOpen Claude setup Guest access + account linking verified by PowMCP
VS CodeOpen VS Code setup Guest access available · Account linking not yet verified
KiroOpen Kiro setup Guest access available · Account linking not yet verified
LM StudioOpen LM Studio setup Guest access available · Account linking not yet verified
Visual StudioOpen Visual Studio setup (Windows) Guest access available · Account linking not yet verifiedCopy one ready-to-send prompt for any agent that supports remote MCP connections.
For clients that require manual configuration, use this app-only endpoint, its JSON entry, or one terminal command.
ChatGPT: enable Developer mode in Settings → Security and login, then add this MCP endpoint from the Plugins page. Availability depends on your account and workspace policy. PowMCP has not yet verified ChatGPT account linking. OpenAI setup guide
https://powmcp.com/ocds-release-package-validate/mcp {
"mcpServers": {
"powmcp-ocds-release-package-validate": {
"type": "http",
"url": "https://powmcp.com/ocds-release-package-validate/mcp"
}
}
}Terminal agents add this app with one command:
claude mcp add --transport http powmcp-ocds-release-package-validate https://powmcp.com/ocds-release-package-validate/mcpcodex mcp add powmcp-ocds-release-package-validate --url https://powmcp.com/ocds-release-package-validate/mcpgemini mcp add --transport http powmcp-ocds-release-package-validate https://powmcp.com/ocds-release-package-validate/mcpManage, disable, or remove this connection in your agent's own MCP settings. PowMCP does not label an external connection as installed without confirmation from that client.
Proof
Check a hosted OCDS release or record package against the standard, its declared extensions, and the lib-cove additional checks, with exact check-and-location evidence
Validate one public Open Contracting Data Standard release or record package against the OCDS JSON Schema, its declared extensions, and the lib-cove additional checks (codelists, deprecated fields, ocid prefix, duplicate ids) with exact check and location evidence, or compare two same-lineage packages before and after a republish, with a clear conformance-versus-data-truth boundary.
Request cost1 completed result
Guests get 50 lifetime app requests. Free accounts get 100 each calendar month.
ocds_package_check
Validates one directly hosted public OCDS (Open Contracting Data Standard) release or record package (a JSON document at a publisher URL whose root carries releases[] or records[] plus links) against the pinned OCDS release/record-package JSON Schema, its declared extensions (10+ resolved and merged from a bundled dated snapshot, falling back to an SSRF-guarded fetch), and the lib-cove-ocds additional checks (closed/open codelist membership, deprecated fields, additional-field cataloguing) run offline by the unmodified lib-cove-ocds engine in an isolated arm's-length subprocess over JSON data only. Auto-detects the OCDS version (1.1 or 1.0). Returns conformance pass/fail, counts by check, findings most-severe-first (schema, then closed-codelist, then advisory) with JSON location and message, the declared-extension resolution inventory, the registered ocid prefix, query-insensitive package-lineage identity, pagination (links.next) presence, and distinguished states (not-an-ocds-package vs a package that fails; version detected vs not-detected vs unsupported; extension resolved vs unresolved). Use for one-package conformance and diagnosis: 'is our release package valid OCDS', 'does it resolve its extensions', 'what conformance problems does it have'. A pass means only that the fetched package satisfied the pinned schema, its extensions, and the additional checks at the named version (NEVER that the contracting data is true, the tenders or awards happened, award values are correct, or the data is complete or non-fraudulent), and it does not validate an unhosted local file or pasted JSON. Offer the AGPL engine's source on request. Downloads a live 0.8-1.2 MB package and runs a schema-plus-extension-plus-additional-checks validation, so a call can take most of the 120-second budget. Tell the user before calling.
ocds_package_compare
Runs the identical pinned lib-cove-ocds validation over exactly two same-lineage directly hosted public OCDS packages (baseline first, revised second) sequentially under one shared deadline, then reports which conformance findings regressed or were resolved. Use only for same-feed pairs: a package and its links.next next-cursor page, or the same canonical package before and after a republish. Returns per-package hashes, detected OCDS versions, pass verdicts and error counts; a comparability note requiring the same detected version, package kind, and query-insensitive package/feed lineage identity; a difference table of finding groups introduced (regressions) and resolved keyed by check and JSON location; and a ranking only when that lineage is established. Use for 'did this republish regress our package', 'which conformance issues changed between the two pages', and page-over-page conformance questions. The ranking orders machine-checkable conformance only (it never means one package's contracting data is truer, more complete, or higher quality), and human review remains required for both. Downloads two live packages and runs two validations, so a call can take most of the 120-second budget. Tell the user before calling.
Other apps for the jobs next to OCDS Package Check.
Scope and boundaries for OCDS Package Check.
Validate the hosted OCDS PPP profile full.json as a release or record package with automatic extension resolution and up to 400 violations, or compare two same-feed package revisions with the baseline URL first.
Read packageState, versionState, and checkState before conforms. Conforms true means zero schema and closed-codelist violations; open-codelist, deprecated-field, additional-field, and other advisory findings may remain, and a missing version is validated as OCDS 1.1. Fix the most severe violations first, verify unresolved extensions separately, and use comparison differences or ranking only when comparable is true; truncation can make them incomplete.
The input must be a directly hosted public package whose root contains releases[] or records[] plus links; pasted JSON and unhosted local files are not accepted. A pass covers the pinned schema, resolved extensions, and lib-cove checks only—it does not verify that procurement events, values, completeness, or absence of fraud are true; comparison requires matching lineage, version, and package kind.