1.2.0npm · specmatic-mcp · latest release
Observed 2026-08-17T19:41:57.874Z using mcpSecurity-inventory. Protocol 2024-11-05.
| Tool | Category | Risk |
|---|---|---|
backward_compatibility_checkCheck for breaking changes in OpenAPI specifications using Specmatic's git-based analysis. Works with relative paths and automatically detects git repository context. Example: targetPath='products_api.yaml'Input schema{
"type": "object",
"properties": {
"targetPath": {
"type": "string",
"description": "File or folder path to analyze for backward compatibility (e.g., 'products_api.yaml' or 'specs/'). If not provided, Specmatic will analyze all tracked specification files"
},
"baseBranch": {
"type": "string",
"description": "Git branch to compare against (optional, defaults to current branch head)"
},
"repoDir": {
"type": "string",
"description": "Repository directory (optional, defaults to current directory)"
}
},
"required": []
} | — | — |
manage_mock_serverManage Specmatic mock servers - start, stop, or list running servers for frontend development. Supports complete mock server lifecycle management.Input schema{
"type": "object",
"properties": {
"command": {
"type": "string",
"enum": [
"start",
"stop",
"list"
],
"description": "The action to perform: 'start' creates a new server, 'stop' terminates a server, 'list' shows running servers"
},
"openApiSpec": {
"type": "string",
"description": "The OpenAPI specification content (YAML or JSON) - required for 'start' command"
},
"port": {
"type": "number",
"default": 9000,
"description": "Port number for the mock server - required for 'start' and 'stop' commands"
},
"specFormat": {
"type": "string",
"enum": [
"yaml",
"json"
],
"default": "yaml",
"description": "Format of the OpenAPI spec - used with 'start' command"
}
},
"required": [
"command"
]
} | — | — |
run_contract_testRun Specmatic contract tests against an API using OpenAPI specificationInput schema{
"type": "object",
"properties": {
"openApiSpec": {
"type": "string",
"description": "The OpenAPI specification content (YAML or JSON)"
},
"apiBaseUrl": {
"type": "string",
"description": "The base URL of the API to test against"
},
"specFormat": {
"type": "string",
"enum": [
"yaml",
"json"
],
"default": "yaml",
"description": "Format of the OpenAPI spec"
}
},
"required": [
"openApiSpec",
"apiBaseUrl"
]
} | — | — |
run_resiliency_testRun Specmatic resiliency tests with boundary condition testing against an API using OpenAPI specification. This enables SPECMATIC_GENERATIVE_TESTS to test how the API handles contract-invalid requestsInput schema{
"type": "object",
"properties": {
"openApiSpec": {
"type": "string",
"description": "The OpenAPI specification content (YAML or JSON)"
},
"apiBaseUrl": {
"type": "string",
"description": "The base URL of the API to test against"
},
"specFormat": {
"type": "string",
"enum": [
"yaml",
"json"
],
"default": "yaml",
"description": "Format of the OpenAPI spec"
}
},
"required": [
"openApiSpec",
"apiBaseUrl"
]
} | — | — |
Compared with initial baseline using full_baseline.
| Risk | Change | Subject |
|---|---|---|
| No material changes recorded. | ||
| Severity | Finding | Advisory |
|---|---|---|
| No confirmed vulnerability is published for this version. | ||
Artifact SHA-256: e9c0f37c1f354027dfcb88cb01d483e71ee2b7061cf61dd088837f88543cf0e7
Scanner: mcp-proof-engine 0.1.0.