Specwise Mcp

io.github.Bytestay由 GitHub 帳號 Bytestay 發布v0.2.4更新於 Nov 6, 2026

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

已驗證STDIO僅桌面開發者工具資料與分析

概覽

AI 產生的概覽

本機 MCP 伺服器,讓程式開發助理透過付費的 Specwise API 驗證 OpenAPI 與 JSON Schema 文件,並比對 OpenAPI 版本的破壞性變更。

可以做什麼
  • 驗證 OpenAPI 3.x 與 Swagger 2.0 文件,逐項列出錯誤的 JSON Pointer、行號與欄號,以及 lint 警告
  • 比對兩個 OpenAPI 3.x 版本(文字、檔案,或檔案對 git 參照),將每項變更標為破壞性、警告、非破壞性或資訊,並提供 semver 建議
  • 驗證 JSON Schema 是否符合其 meta-schema,並可選擇檢查資料是否符合該 schema
  • 回傳 API 的 JSON 回應,市場有回報時附上剩餘額度
適用情境
適合在助理編輯或審查 API 契約時使用,自動完成驗證與破壞性變更偵測,例如發佈前把修改後的規格與 git 分支比對。
執行需求
透過 uvx 以 stdio 在本機執行(需 Python 3.10+,由 uv 安裝)。需要 RapidAPI 金鑰(RAPIDAPI_KEY)或 api.market 金鑰(API_MARKET_KEY);兩者都設定時以 HFL_MARKETPLACE 選擇市場。需要連線至 Specwise API 與所選市場的網路。僅支援桌面用戶端。
安裝前請注意
每次工具呼叫都會用掉付費方案的一次請求;免費 Basic 方案每月 15 次且為硬性上限。僅在傳入路徑時讀取本機檔案,但檔案內容會隨該次請求傳送給 Specwise API。金鑰只會傳送給所選市場。不會抓取外部 $ref,Swagger 2.0 只能驗證不能比對。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Specwise Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Specwise MCP server

[M8ven Score] [CI] [PyPI] [Python 3.10+] [License: MIT]

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
RapidAPIplans
api.marketstore

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):

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

Claude Code:

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

Environment

variablemeaning
RAPIDAPI_KEYyour RapidAPI key
API_MARKET_KEYyour api.market key, used when RAPIDAPI_KEY is not set
HFL_MARKETPLACErapidapi or apimarket, when both keys are set

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

Also listed on Glama:

[specwise-mcp on Glama]

3. Tools

toolwhat 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

bash
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 ByteStay.

來源:README.md,提交 c8e39d9

工具

0
SourceWeft 曾在隔離沙箱中以無憑證方式啟動該軟體包一次,以列出其工具,但未能完成:該軟體包類型無法在沙箱中執行。

版本歷史

1
  1. v0.2.4最新Nov 6, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分