Daily MCP Registry Digest

Overview

ai.preclick/preclick-mcp updated to 0.3.2 (updatedAt/statusChangedAt: 2026-03-29). Hosted URL preflight scanning service (X-API-Key optional for trial; required for higher limits).
ai.trendsmcp/trends updated to 1.0.2 (updatedAt/statusChangedAt: 2026-03-29). Trend data server now clearly requires Authorization: Bearer header for access.
ai.nefesh/human-state published as 1.0.0 (updatedAt/statusChangedAt: 2026-03-28). New remote endpoint for human state fusion signals.

Endpoint and transport shifts are common in recent updates (e.g., some projects moved from SSE to streamable-http in their version history). Ensure your clients can follow the registry’s isLatest entry and re-validate the configured remote URL/transport when upgrading.
Auth posture tightening: multiple servers now explicitly require bearer tokens or API keys in headers; treat headers marked isSecret as secrets and ensure they are injected via your secret manager rather than configs checked into source control.

Prevent breakage during upgrades: latest versions may change connection details (remote URL, transport type, or required headers). Pin versions in production and roll forward with a canary when a server’s latest changes.
Security and compliance: new/clarified auth requirements (notably for Trends MCP) mean agents may fail without correct secret injection; also reduces accidental anonymous usage and limits abuse.
Policy and egress control: new endpoints (e.g., Nefesh, Trends, PreClick) may require allowlist updates, TLS inspection exceptions, or updated outbound routing rules.

Review deployments using ai.preclick/preclick-mcp and ai.trendsmcp/trends for required headers and rate/plan constraints.
If you auto-track latest, add a health-check + tool smoke test step on registry updates before promoting to production.
Update network allowlists for newly introduced/changed endpoints where applicable.