Fix: Correct URI query parameter matching and class name typo (Fixes #596)

[sheegansrigm]

Motivation and Context

This pull request addresses two separate issues, with the primary goal of resolving issue #596.

Fixes: #596

1. URI Matching Bug: A critical bug was identified in DefaultMcpUriTemplateManager.matches() where it would fail to correctly match any URI template containing a query parameter (e.g., file://name/search?={search}). The root cause was the unescaped ? character being misinterpreted as a special character by the regex engine.

2. Class Name Typo: Incorporates a pending change to correct a persistent spelling mistake in a core factory class name (DefaultMcpUriTepmlateManagerFactory).

Description of Changes

1. Bug Fix: The matches method in DefaultMcpUriTemplateManager has been rewritten to use a robust regex-building approach with Pattern.quote(). This ensures that all literal parts of the URI template, including special characters like ?, are properly escaped before the matching pattern is compiled. The logic now mirrors the safer implementation already used in the extractVariableValues method.

2. Typo Fix: The class DefaultMcpUriTepmlateManagerFactory has been renamed to DefaultMcpUriTemplateManagerFactory, and all references to it have been updated throughout the codebase.

How Has This Been Tested?

• Two new unit tests (shouldMatchUriWithQueryParameters and shouldExtractVariableValuesFromUriWithQueryParameters) were added to specifically reproduce the URI matching bug.
• After applying the fix, both new and all pre-existing unit tests pass locally, confirming that the bug is resolved and no regressions have been introduced.
• The project compiles and builds successfully with the renamed factory class.

Breaking Changes

[x] Yes. Any user directly referencing the misspelled class DefaultMcpUriTepmlateManagerFactory will need to update their code to use the corrected class name DefaultMcpUriTemplateManagerFactory after pulling this change.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

This is a straightforward find-and-replace action to correct a typo. No other logic or functionality has been altered.

[tzolov]

Thank you @sheegansrigm
LGTM

[sheegansrigm]

Thanks for the review @tzolov

[sheegansrigm]

Hi @tzolov

I just pushed a new commit to address the CI build failure. It looks like my changes had some minor formatting violations that the spring-javaformat check caught.

​I've fixed this by running mvn spring-javaformat:apply as the log suggested. The automated checks should all pass now.

[TheTerribleChild]

@sheegansrigm
Thanks for getting this fix in so quickly!

I have tested this and it is working.

Another issue I found with the query parameter is if it is not defined in the request, it will fail to match the template. According to the specs, if query parameter is undefined, then it should not be set.

Example Template:

file://folder?pageNum={pageNum}&limit={limit}

Failed URI match:

file://folder?pageNum=10
file://folder