Specwise
# hybridforgelab-specwise-mcp: moved to bytestay-specwise-mcp
This package has moved to **[bytestay-specwise-mcp](https://pypi.org/project/bytestay-specwise-mcp/)**. Hybrid Forge Lab is now ByteStay.
This last version only installs bytestay-specwise-mcp and forwards to it. It prints a one-line notice on stderr and gets no more updates.
## Switch
Replace `hybridforgelab-specwise-mcp` with `bytestay-specwise-mcp` in your MCP client config:
```json
"command": "uvx",
"args": ["--from", "bytestay-specwise-mcp", "specwise-mcp"]
```
Or with Claude Code:
```bash
claude mcp add specwise --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from bytestay-specwise-mcp specwise-mcp
```
The environment variables are the same, so your keys keep working.
## Links
- Package: [bytestay-specwise-mcp](https://pypi.org/project/bytestay-specwise-mcp/)
- Source: [Bytestay/specwise-mcp](https://github.com/Bytestay/specwise-mcp)
- Specwise API: [specwise.bytestay.pt](https://specwise.bytestay.pt)
TDQS
Scored across 3 tools
Each tool targets a clearly distinct operation: validation of OpenAPI, diffing of OpenAPI, and JSON Schema validation. While validate_openapi and validate_json_schema both validate, the domains (OpenAPI document vs. JSON Schema + data) are explicitly separated, leaving no realistic ambiguity.
All three tools follow a strict verb_object pattern: validate_openapi, diff_openapi, validate_json_schema. Predictable and consistent throughout.
Three tools is slightly thin for a spec-tooling server, but each is a distinct, well-scoped capability with no filler. A 3-tool set is on the low edge of the ideal band but defensible for a focused lint/diff utility.
The core spec lifecycle for validation and comparison is covered, including breaking-change detection and semver suggestions. Gaps exist around formatting/bundling or schema conversion, but agents can work around these; the surface is coherent for a focused toolset.