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 是否符合其元模式,并可选地检查数据是否符合该 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 分