io.github.hybridforgelab/specwise-mcp
io-github-hybridforgelab-specwise-mcp declares 3 capabilities across 3 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
3 of 3 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
3 of 3 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
3 of 3 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
3 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
validate_openapi | read |
declared |
diff_openapi | read |
declared |
validate_json_schema | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-11-03 | 5 | tools/list answered by the PyPI package hybridforgelab-specwise-mcp==0.2.0 (published to PyPI as hybridforgelab-specwise-mcp, listed in the official MCP registry as io.github.hybridforgelab/specwise-mcp 0.2.0), run in an isolated container with no network access and placeholder credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.