Skip to content
Summary
- Total updated servers: 16
- Deprecated servers: 0 observed
- Deleted servers: 0 observed
Notable changes
- TrendsMCP expansion and refresh: Trends MCP advanced to 1.0.4 and introduced/updated a broad suite of dedicated endpoints at 1.0.3 (Google Trends, YouTube, TikTok, Reddit, Amazon, App Store, Spotify, Steam, Wikipedia, X/Twitter, npm) plus news sentiment and news volume endpoints at 1.0.1. Most endpoints now require Bearer API auth.
- PreClick updated: ai.preclick/preclick-mcp moved from 0.2.0 to 0.3.2 (hosted URL preflight/scanning service). Note: ai.urlcheck/urlcheck-mcp remains listed as “formerly URLCheck” under the PreClick branding, implying a parallel listing to track.
- Pictomancer endpoint change: ai.pictomancer/image-processing updated from 0.1.0 to 0.2.0 and shifted remote base URL from https://mcp.pictomancer.ai/mcp to https://api.pictomancer.ai/mcp.
Why it matters for operators
- Auth and key management impact: The newest TrendsMCP endpoints commonly require Authorization: Bearer …. Expect configuration updates in MCP client/server catalogs, secret stores, and runtime env var injection if you roll these out broadly.
- Endpoint drift and allowlists: The Pictomancer host change (
mcp.* → api.*) can break strict egress policies, DNS allowlists, or service meshes unless updated.
- Vendor rename/duplicate listings risk: PreClick and the legacy URLCheck-branded entry may both exist in inventories; operators should dedupe, confirm which hostname is supported, and update documentation to avoid onboarding the wrong endpoint.
- Fleet hygiene: No explicit deprecations/deletions were present in this dataset, but multiple projects maintain several historical versions side-by-side—ensure your automation pins isLatest=true unless you intentionally freeze versions.
