Skip to main content

Specwise MCP server

Let your coding agent check an API contract: validate an OpenAPI document, find the breaking changes between two versions (also against git), and validate JSON Schemas and data.

The server is open source (MIT). It calls the Specwise API, which is paid, with a free plan.

  • You use your own key, from RapidAPI or api.market.
  • Every tool call is one request on your plan.
  • The free Basic plan has 15 requests a month, with a hard limit, so it never runs up a bill.

1. Get a key

marketplace
RapidAPI plans
api.market store

2. Add the server to your MCP client

The server runs locally over stdio with uv. Put your key in its environment.

JSON configuration (Claude Desktop, Cursor, VS Code and most clients):

{
  "mcpServers": {
    "specwise": {
      "command": "uvx",
      "args": ["--from", "hybridforgelab-specwise-mcp", "specwise-mcp"],
      "env": { "RAPIDAPI_KEY": "your-rapidapi-key" }
    }
  }
}

Claude Code:

claude mcp add specwise --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from hybridforgelab-specwise-mcp specwise-mcp

Environment

variable meaning
RAPIDAPI_KEY your RapidAPI key
API_MARKET_KEY your api.market key, used when RAPIDAPI_KEY is not set
HFL_MARKETPLACE rapidapi or apimarket, when both keys are set

Without a key the server still starts. The first tool call then explains where to get one.

3. Tools

tool what it does
validate_openapi(spec=… | spec_path=…) every error with its JSON Pointer, line and column, plus lint warnings (OpenAPI 3.x and Swagger 2.0)
diff_openapi(...) each change between two OpenAPI 3.x versions is breaking, warning, non-breaking or info, with a semver suggestion
validate_json_schema(schema=… | schema_path=…, instance=… | instance_path=…, draft=None) checks the schema against its meta-schema and, if given, the data against the schema

diff_openapi takes the two versions in one of three ways:

  • base and revision as text;
  • base_path and revision_path as files;
  • revision_path with base_git_ref. For example, after editing a spec: revision_path="openapi.yaml", base_git_ref="main".

Every tool returns the API's JSON response.

  • When the marketplace reports it, quota_remaining is added: the requests left on your plan this month.
  • Errors are explained in plain words, with what to do next:
    • key refused, with the link to subscribe;
    • quota reached, with the plans;
    • input the API couldn't process, with the API's reason.

Privacy

  • Local files are read only when a tool is given their path. They are sent to the API for that one request.
  • The API processes inputs in memory and doesn't store them. See the privacy policy.
  • Your key is only sent to the marketplace you chose.

Limits

  • Documents up to about 900 KiB each.
  • External $refs are not fetched. Bundle multi-file specs first (redocly bundle).
  • The diff needs OpenAPI 3.x; Swagger 2.0 can be validated, not diffed.
  • The server needs Python 3.10+ (uv installs it for you).

Development

uv venv && uv pip install -e ".[dev]"
.venv/bin/pytest            # unit tests, no network; 100% coverage required
.venv/bin/ruff check src tests scripts

scripts/e2e_stdio.py specwise runs the server over stdio, as a client would, and calls its tools against the real API. It needs RAPIDAPI_KEY or API_MARKET_KEY.

Licence

MIT. Specwise itself is a paid API with a free plan, run by Hybrid Forge Lab.

Metadata

Release files for hybridforgelab-specwise-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hybridforgelab-specwise-mcp 0.1.0
File Size Uploaded Provenance Actions
hybridforgelab_specwise_mcp-0.1.0.tar.gz 12.2 kB With provenance Details for hybridforgelab_specwise_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hybridforgelab-specwise-mcp 0.1.0
File Interpreter ABI Platform Actions
hybridforgelab_specwise_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for hybridforgelab_specwise_mcp-0.1.0-py3-none-any.whl

Total release size: 21.7 kB

Release files / hybridforgelab_specwise_mcp-0.1.0.tar.gz

Download URL hybridforgelab_specwise_mcp-0.1.0.tar.gz
Size 12.2 kB
Tags Source
SHA-256 checksum
How to use checksums
7c7d61fc19a4b2b4c55db5d2abb81393f1bf62e480d24bf85f7f772fbe1b5604
BLAKE2b-256 checksum
How to use checksums
b3ba52535419dbae9d035b157c60098ff6f0ab0982c07b0a6c93d9cb6c071c74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

Release files / hybridforgelab_specwise_mcp-0.1.0-py3-none-any.whl

Download URL hybridforgelab_specwise_mcp-0.1.0-py3-none-any.whl
Size 9.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
775167576cffe849562b65af095a191842a80364ee4b42329638eb4b92c856a5
BLAKE2b-256 checksum
How to use checksums
92a0daafb145eabfec17c83356ef9c46aec7295d7223e525bd5336d606c35075
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

Security for hybridforgelab-specwise-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for hybridforgelab_specwise_mcp-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page