{"id":"skernelx-mysearch-proxy","name":"MySearch-Proxy","af_score":61.5,"security_score":56.2,"reliability_score":35.0,"what_it_does":"MySearch-Proxy is a unified search backend for AI agents, bundling an MCP server and skills plus a deployable proxy/console. It routes queries to upstream providers (Tavily, Firecrawl, Exa, optional X/Social), manages provider health and auth errors, provides token/key/quotas syncing via the proxy layer, and offers MCP tools (search, extract_url, research, mysearch_health) accessible over stdio/HTTP/SSE.","best_when":"You want to plug an MCP-based search capability into AI tooling while centralizing provider configuration/health checks behind a proxy service.","avoid_when":"You cannot tolerate dependency on multiple third-party search providers (Tavily/Firecrawl/Exa/X/Social) or you require strict guarantees about data residency/compliance, which are not described here.","last_evaluated":"2026-03-30T13:47:54.061198+00:00","has_mcp":true,"has_api":false,"auth_methods":["API key (MYSEARCH_PROXY_API_KEY / MYSEARCH_* env vars)","Admin password for proxy console (ADMIN_PASSWORD env var)","Upstream provider keys configured in proxy"],"has_free_tier":false,"known_gotchas":["Caching is TTL-based and in-process; single CLI invocations may not benefit across processes (explicitly noted).","If upstream provider auth fails, routing behavior changes: routes/docs/resource skip providers marked with auth_error.","Firecrawl 'site:' empty-results triggers fallback logic; agents expecting strictly site-filtered results may see broader follow-up retrieval."],"error_quality":null}