MCP Registry v1.8.5
MCP Registry v1.8.5 introduces enhanced performance diagnostics for ingress and database operations, adds support for GitLab nested subgroups, and applies stricter metadata validation rules.
Why this signal matters
MCP Registry v1.8.5 introduces production diagnostics covering request arrivals, backlog, database pool and query metrics, and bounded slow-listing logs correlated with ingress request IDs. Slow-request logs delineate connection acquisition, query and fetch waits, row decoding, and response processing, capturing snapshots during hanging requests. Note that ingress cache and timing log fields necessitate corresponding infrastructure updates. On the validation and publisher side, the release enforces fixed-width padding for ECDSA P-384 signatures, captures repository IDs at initialization to survive renames, enables GitLab repository URLs with nested subgroups, and rejects incomplete repository metadata along with invalid or empty positional arguments. Existing invalid metadata must be corrected when editing or republishing. No database migrations are included in this release.
Actionable summary
MCP Registry release v1.8.5 adds granular observability metrics (request backlog, DB pool/query wait, slow-request logs) and introduces validation changes including ECDSA P-384 signature padding, GitLab subgroup support, and stricter rejection of incomplete metadata and invalid arguments.
- Agent usefulness
- 62/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Verify and correct any previously stored metadata before republishing or editing, as incomplete repository metadata and invalid arguments are now rejected.
- Ensure the accompanying infrastructure rollout is applied if utilizing ingress cache and timing log fields.
- Verify publisher configurations if relying on ECDSA P-384 signatures or GitLab nested subgroup repository URLs.