check_specific
Run a named subset of validation checks on a file
How to use it
check_specific is exposed by the Twincat Validator MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the check_specific tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install Twincat Validator MCP
pip install twincat-validator-mcpOther tools in Twincat Validator MCP (16)
Apply auto-fixes to multiple files matching glob patterns
Apply all safe auto-fixes to a single file in deterministic order
Promote inline METHOD blocks from the main ST declaration into proper <Method> XML elements
Generate a canonical, deterministic XML skeleton for a given file type and subtype
Return curated knowledge-base entries and OOP policy scoped to a workflow stage (pregeneration or troubleshooting)
Resolve the active OOP validation policy for a file or directory (walks ancestor dirs for .twincat-validator.json)
Return a 0–100 health score with issue counts by severity
Validate the nearest .twincat-validator.json config file — checks key names, types, and value ranges
Full enforced pipeline across multiple files with summary or full response modes
Full enforced pipeline for one file: validate → autofix → validate → suggest fixes if still unsafe
Generate prioritized fix recommendations from a validation result
Validate multiple files matching glob patterns (e.g. ["/.TcPOU"])
Full validation of a single file — returns all issues with severity, location, code snippet, and explanation
Quick critical-only check to confirm a file is safe to import into TwinCAT
Run the strict pipeline twice and report per-file idempotence stability