MCP servers · bytestay

Specwise MCP server: OpenAPI and JSON Schema validation and diffs

An MCP server that lets a coding agent validate OpenAPI and JSON Schema documents and compare OpenAPI versions for breaking changes, using a paid API with a free plan.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server gives a coding agent three tools. validate_openapi checks an OpenAPI 3.x or Swagger 2.0 document and reports each error with its JSON Pointer, line and column, plus lint warnings. diff_openapi compares two OpenAPI 3.x versions and labels each change as breaking, warning, non-breaking or info, with a semver suggestion. It can take the versions as text, as files, or as a revision file compared against a git ref such as main. validate_json_schema checks a schema against its meta-schema and, when data is supplied, checks that data against the schema.

An agent would typically use it while editing an API contract, to confirm the spec is valid or to see whether a change would break existing clients before it is merged. The server is open source under the MIT licence and runs locally over stdio.

It calls the paid Specwise API with your own key from RapidAPI or api.market, and each tool call counts as one request on your plan. Local files are read only when a tool is given their path and are sent to the API for that single request, which processes them in memory without storing them. Responses are the API's JSON, with a quota_remaining field added when the marketplace reports it.

Limitations and requirements

Requires your own API key from RapidAPI or api.market; without a key the server starts but tool calls fail until one is set. The free Basic plan allows 15 requests a month with a hard limit. Documents are limited to about 900 KiB each. External $refs are not fetched, so multi-file specs must be bundled first. The diff needs OpenAPI 3.x; Swagger 2.0 can be validated but not diffed. Requires Python 3.10 or later.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.Bytestay/specwise-mcp

    OpenAPI and JSON Schema validation and OpenAPI breaking-change diffs for AI agents.

    v0.2.9
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026