Legacy System Pattern Matcher

Legacy System Pattern Matcher MCP Connector for Claude

A+

Identifies legacy code patterns and provides deterministic rules for safe interaction.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner

This MCP server acts as a diagnostic bridge for AI agents working on aging codebases. It scans for framework-specific signatures, custom ORM patterns, and non-standard directory structures. Once identified, it provides deterministic interaction rules such as do_not_modernize or wrap_dont_replace to prevent accidental regressions. Use scan_codebase to detect patterns, get_pattern_details to retrieve specific protection requirements, and calculate_risk_assessment to evaluate the danger level of modifying specific files.

legacy-codepattern-matchingrisk-assessmentcodebase-analysisrefactoring-safety

3 tools expose this connector's capabilities to your AI agent.

calculate_risk_assessment

scan_codebase

get_pattern_details

See how to talk to your AI agent using Legacy System Pattern Matcher.

Scan the current directory for legacy patterns.

I have scanned the codebase. I detected 3 legacy patterns: an AngularJS module in `src/legacy/app.js`, a jQuery AJAX call in `src/legacy/utils.js`, and a custom ORM pattern in `src/db/connection.js`. The legacy density score is 0.45.

What is the risk level of modifying `src/legacy/app.js`?

The risk level for `src/legacy/app.js` is critical. The density score is 0.8, and the `do_not_modernize` rule is active, meaning you should not attempt to rewrite this file.

Get the rules for the pattern found in `src/legacy/utils.js`.

The applicable rules for the pattern in `src/legacy/utils.js` are `wrap_dont_replace` and `preserve_api_surface`.

The tool uses deterministic AST and regex pattern matching to identify specific architectural or syntactical markers in the codebase.

Related Connectors