Inspect supplied OpenAPI and MCP definitions and check requests, responses and schema compatibility within explicit profiles.
How to choose
Use linting for supported document rules, request/response checks for a supplied exchange, and compatibility checks for the declared schema subset. Read unsupported keywords before choosing.
No remote API execution, exhaustive protocol conformance or guarantee that a described service behaves as declared.
Find actionable agent-integration problems in supplied OpenAPI 3.1.x JSON: unique operation IDs, response shape, path parameters and security references. Paths-only lint; references are reported without resolution. At most 100 paths/200 operations/200 retained findings; not full specification validation.
Choose for: Review an OpenAPI 3.1 contract before wiring an agent client Locate repairable contract defects with JSON Pointer findings Find duplicate operation IDs, missing path parameters and response definitions
Outside this profile: Full OpenAPI conformance or remote reference resolution Authentication/security certification
Extract a bounded agent planning inventory of methods, templates, parameters, media types, response codes, and effective security declarations from OpenAPI 3.1.x. Reports lint coverage and unresolved references; does not call endpoints or resolve schemas.
Choose for: Plan which API operations and authentication schemes an agent needs Audit operation coverage before client generation
Outside this profile: Discovering live endpoint availability Resolving referenced parameters or testing credentials
Conservatively test whether all values accepted by a previous typed JSON Schema subset remain accepted by a next schema. Returns compatible only after a structural inclusion proof, incompatible only with a verified counterexample, otherwise unknown. Supports explicit single types, object/array constraints, enum/const and inclusive bounds; no refs/combinators/regex.
Choose for: Gate an agent tool input-schema upgrade for backward acceptance Get concrete evidence for a breaking schema change
Outside this profile: General JSON Schema subsumption Deciding behavior compatibility or security from schemas alone
Wrap a supported object-root JSON Schema in a deterministic MCP tool descriptor, optionally with an object-root output schema. Rejects unsupported keywords instead of silently weakening constraints. Does not deploy a tool, execute code, or claim provider-specific strict function compatibility.
Choose for: Create a named MCP tool descriptor from an object input schema Adapt a bounded JSON object schema into a tool definition Preserve schema constraints during tool registration preparation
Outside this profile: OpenAI strict-mode conversion or arbitrary JSON Schema conversion Installing or running an MCP server
Lint a supplied MCP tool descriptor for a bounded naming profile, description quality, object-root input/output schemas and typed annotation hints. Unsupported schemas produce explicit findings. Annotations are untrusted hints; this is neither full MCP protocol validation nor a security decision.
Choose for: Review tool descriptors before adding them to an agent catalogue Identify schema limitations and untrusted annotation hints
Outside this profile: MCP transport/protocol conformance certification Trusting readOnlyHint as an authorization guarantee
Check already-deserialized supplied parameter values and an optional JSON body against one exact OpenAPI 3.1 path-template/method. Applies the typed-schema subset only; references, serialization, authentication, parameter content and non-JSON bodies are not evaluated. Reports unsupported coverage separately from invalid values; never sends the request.
Choose for: Preflight a typed API request before paying for or executing it Find missing required parameters and incompatible JSON bodies
Outside this profile: Validating raw URL encoding, serialization, auth or live behavior Resolving OpenAPI references or arbitrary JSON Schema
Compose invalid payloads from a caller-supplied valid seed with one structural edit, an exact target assertion and the complete bounded failed-assertion set.
Choose for: generate targeted negative request payloads from a valid JSON seed and supported schema compose one-edit contract violations with checked constraint isolation
Outside this profile: Target rejection guarantees, expected HTTP status, fuzz attacks or a mutation-testing score A valid seed is missing or incompatible with the supported structural schema Arbitrary JSON Schema, formats, regexes, references, combinators, nested objects or nested arrays Executing target tests, fetching services, running supplied code or proving security