Server data from the Official MCP Registry
OpenAPI and JSON Schema validation and OpenAPI breaking-change diffs for AI agents.
About
OpenAPI and JSON Schema validation and OpenAPI breaking-change diffs for AI agents.
Security Report
Valid MCP server (1 strong, 2 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (4/4 approved).
10 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: RAPIDAPI_KEY
Environment variable: API_MARKET_KEY
Environment variable: BYTESTAY_MARKETPLACE
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"bytestay-specwise-mcp": {
"command": "uvx",
"args": [
"bytestay-specwise-mcp==0.2.9"
],
"env": {
"RAPIDAPI_KEY": "your-rapidapi-key-here",
"API_MARKET_KEY": "your-api-market-key-here",
"BYTESTAY_MARKETPLACE": "your-bytestay-marketplace-here"
}
}
}
}Some servers take additional arguments. See the repository for details.
Documentation
View on GitHubFrom the project's GitHub README.
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
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", "bytestay-specwise-mcp", "specwise-mcp"],
"env": { "RAPIDAPI_KEY": "your-rapidapi-key" }
}
}
}
Claude Code:
claude mcp add specwise --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from bytestay-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 |
BYTESTAY_MARKETPLACE | rapidapi or apimarket, when both keys are set |
Up to 0.2.7 the setting was HFL_MARKETPLACE. The old name still works, with a one-line notice on stderr.
Without a key the server still starts. The first tool call then explains where to get one.
Also listed on Glama:
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:
baseandrevisionas text;base_pathandrevision_pathas files;revision_pathwithbase_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_remainingis 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.
History
Formerly Hybrid Forge Lab. This repository continues hybridforgelab/specwise-mcp under the ByteStay name since November 2026, so the older commits come from there.
Licence
MIT. Specwise itself is a paid API with a free plan, run by ByteStay.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
