Compatibility And Validation
MCP-AQL conformance is currently defined by normative behavior requirements in the specification and an in-progress validation track. This page clarifies what can be asserted today versus what is still being built.
On this page
Jump to a section
Use the outline to move through longer pages without losing your place.
Related reading
Go Deeper In The Full Spec
The detail behind compatibility claims and test scope lives in the longer conformance-oriented spec pages.
Related Summary Pages
Conformance lands best when read alongside the protocol rules, error surface, and launch scope.
Baseline Requirements
- Implement runtime introspection for operation discovery
- Expose CRUDE or single-endpoint mode routing
- Return discriminated success/error response unions
- Document operation contracts in introspection output
Current Validation Posture
Available Now
Ready- Normative spec-backed conformance requirements
- Schema validation workflows in specification repo
- Manual profile review against spec requirements
In Progress
Active workstream- Dedicated conformance validator CLI
- MVP "on-spec" validator profile for third-party servers
- Expanded semantic evaluation and usability-focused tests
Launch Guidance
For preliminary public launch, implementations should be positioned as draft-compatible with transparent known gaps. The site should distinguish between:
- Normative requirements (must follow to claim compatibility)
- Operational maturity signals (what testing and tooling already exists)
- Remaining hardening work (what is explicitly not final yet)
Validator Track
The validator track is being developed in MCPAQL/tools. Current planning includes both a general conformance CLI
and an MVP profile specifically targeting "on-spec" checks for third-party MCP-AQL implementations.
Public messaging should avoid implying final certification until validator and conformance tracks are complete.