Exposes Specmatic's API contract testing, resiliency testing, and mocking capabilities to AI coding agents via natural language, enabling automated validation and simulation of API behaviors
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Version 1.2.0 declares 1 executable entrypoint.
npm install --save-exact specmatic-mcp@1.2.0npx -y -p specmatic-mcp@1.2.0 specmatic-mcp{
"mcpServers": {
"specmatic-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"specmatic-mcp@1.2.0",
"specmatic-mcp"
]
}
}
}| Canonical slug | specmatic-mcp-server-e32f0033 | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:specmatic-mcp | Repository | specmatic/specmatic-mcp-server |
| First published | — | Latest release | — |
| Last security verification | — | Classification confidence | 90% |
| Publication | Published | Official distribution | Yes |
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | specmatic-mcp | 1.2.0 | 1 | Repository |
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npmspecmatic-mcp | 1.2.0Current | Sep 5, 2026 | 4 toolsSucceeded · 0 resources · 0 prompts | Failed |
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
| Provenance | artifact_hash_verified | Signature | — |
|---|---|---|---|
| MCP SDK | @modelcontextprotocol/sdk | Artifact SHA-256 | e9c0f37c1f354027dfcb88cb01d483e71ee2b7061cf61dd088837f88543cf0e7 |
| Scanner | mcp-proof-engine 0.1.0 | Scan completed | Aug 20, 2026 |
| Security rating | 35 / 100 | Methodology | version-rating-1.0 |
[ "specmatic-mcp" ]
[ "security_policy_not_observed" ]
| Tool | Category | Annotations | 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"
]
} | — | — |
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Install the selected package version with: npm install --save-exact specmatic-mcp@1.2.0
Specmatic MCP Server exposed 4 tools during independent protocol observation, including backward_compatibility_check, manage_mock_server, run_contract_test, run_resiliency_test.
Our scanner tested version 1.2.0 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.
Curated product and capability guides containing this catalog record.