MCP Registry v1.8.6
MCP Registry v1.8.6 improves search performance under mixed traffic and introduces a minimum 3-character requirement for search terms.
Why this signal matters
MCP Registry v1.8.6 focuses on search performance optimization under mixed search, pagination, and publishing traffic. Key technical changes include selecting search page keys using covering indexes prior to fetching complete records, planning search queries based on actual parameter values for broad and rare terms, and optimizing namespace suffix searches. Non-empty search queries must now consist of at least three Unicode characters; searches failing this constraint will return HTTP 422. Deployment instructions recommend prebuilding and concurrently verifying indexes for migrations 016/017 on busy databases, noting that validated burst capacity relies on a 3-CPU PostgreSQL quota on existing nodes without changes to the application connection pool.
Actionable summary
MCP Registry v1.8.6 enhances search query performance via covering indexes, parameter-specific query planning, and namespace suffix optimizations. Breaking change: search terms under three Unicode characters now return HTTP 422.
- Agent usefulness
- 62/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Ensure client search queries provide at least three Unicode characters to prevent HTTP 422 errors.
- Prebuild and verify migrations 016 and 017 indexes concurrently on busy databases prior to deployment.
- Review deploy/README.md and tools/readbench/STAGING SEARCH RESULTS.md for full deployment procedures, benchmarks, and limitations.