The official MCP Registry now rejects searches under three characters. With an error.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On 27 October 2026 the official MCP Registry shipped v1.8.6. Any non-empty search term must now be at least three Unicode characters, and shorter ones get HTTP 422. The same release reworks how search pages are fetched, to hold up under mixed search, pagination and publishing traffic.
Why it matters
Picture a user typing "gi" into your server picker: yesterday it returned results, now it returns an error. Autocomplete boxes and sync jobs are where a two-letter query quietly hides.
What to do
Search your code for calls to the registry search with user input. Hold back terms under three characters before the request, and treat a 422 as an empty result, not a crash.

My take
Lior Aharonov
Founder, 7IT Solutions
Performance releases are the ones nobody reads. They are also the ones that change what your users see the next morning.
Sources
| MCP Registry v1.8.6 release notes | github.com |
Researched with AI tools; every fact is checked against the linked sources.