Skip to content
Snapshot
- Total updated servers (new latest versions/records): 10
- Deprecated servers: 0 (none marked)
- Deleted servers: 0 (none present/marked)
Updated servers (latest version changes)
- ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (docs/website URL updated; auth header guidance updated).
- ai.adramp/google-ads: 1.0.0 → 1.0.3 (transport shifted off SSE; now streamable-http at https://mcp.adramp.ai; added website URL in latest).
- ai.cookiy/cookiy: 1.7.5/1.7.6/1.7.7/1.7.9 → 1.7.19 (description/packaging metadata refreshed; latest points to hosted streamable-http https://s-api.cookiy.ai/mcp).
- ai.kawacode/mcp: 5.0.2 → 5.0.4 (website URL changed to kawacode.ai; npm package version alignment fixed in latest).
- ai.marketcore/mcp: 1.0.0/1.0.1 → 1.0.2 (title/website/icons normalized; keeps both streamable-http and SSE endpoints).
- ai.mcpanalytics/analytics: 1.0.4 → 1.0.5 (same remote endpoint; version bump).
- ai.mcpcap/mcpcap: 0.6.4 → 0.9.6 (rapid pypi-version progression; stdio transport).
- ai.namewhisper/ens-tools: 1.0.0/1.0.1 → 1.0.2 (tooling scope wording updated; same remote endpoint).
- ai.openmandate/mcp: 0.3.1/0.3.2/0.3.3/0.5.0 → 0.5.1 (remote stabilized at https://mcp.openmandate.ai/mcp; description now emphasizes posting mandates & matching).
- ai.pictomancer/image-processing: 0.1.0 → 0.2.0 (remote URL migrated from https://mcp.pictomancer.ai/mcp to https://api.pictomancer.ai/mcp).
Notable changes (operator-impacting)
- Transport/endpoint changes that may break clients:
- Adramp Google Ads: SSE endpoint replaced by streamable-http in later versions.
- Pictomancer: remote base URL changed (mcp.* → api.*).
- OpenMandate: earlier version used https://api.openmandate.ai/mcp; later versions standardize on https://mcp.openmandate.ai/mcp.
- Auth/header requirements clarified or introduced:
- Trends MCP (1.0.1) requires Authorization bearer key (already latest in this data slice, but relevant for deployments).
- AdAdvisor, OpenMandate continue to require Bearer tokens; documentation links updated.
- Rapid version churn to watch:
- mcpcap shows multiple sequential releases in a short window; expect behavioral/tool changes and update your pinning strategy.
- Marketgenius publishes frequent date-stamped versions (latest: 2026-03-28); treat as a continuously deployed service.
Why it matters for operators
- Endpoint drift is the #1 availability risk: remote URL and transport changes (SSE vs streamable-http) can cause immediate connection failures if configs are pinned to older endpoints.
- Version pinning vs auto-updates: fast-moving servers (e.g., mcpcap, Marketgenius) increase regression risk; operators should pin known-good versions and schedule controlled rollouts.
- Secrets management remains mandatory: more servers rely on Authorization-style headers and other secret inputs; ensure your MCP runtime injects secrets via vault/secret store and never through static config committed to repos.
