Model providers answer questions or create embeddings. MCP providers remain a separate protected integration surface for external product actions. A Google model provider and a Google Gmail MCP connection are separate integrations with separate credentials, policies, and ownership.

Do not put MCP OAuth credentials into the normal model-provider configuration. MCP uses dedicated provider profiles and dedicated per-user connection records so existing Google, GitHub, Drive, and other integrations remain compatible.

Add SearXNG (Self-hosted) from the Web provider tab and enter the URL reachable by the AverQel API, for example http://searxng:8080 when both services share a private Docker network. SearXNG must have its JSON search format enabled. No API key is required.

DeepSpace invokes the bounded web_search tool only when the selected model requests it. Results are fetched server-side, filtered by the configured domain policy, and returned with titles, URLs, snippets, source engines, and available publication dates. The final Markdown response receives a Sources section with links.

Requests use bounded timeouts, Redis-backed per-user rate limits, redirect blocking, URL validation, and endpoint SSRF checks. The model never receives shell or cURL access; it receives only the typed web-search tool and sanitized result data. MCP remains a separate integration surface.

1. AverQel publishes a curated marketplace entry with the official remote endpoint, reviewed tools, requested scopes, and risk policy.
2. An administrator configures AverQel's Google or GitHub OAuth client ID, client secret, and exact callback URI on the VPS.
3. The user selects Connect and is redirected to Google or GitHub.
4. The provider returns an authorization result to AverQel's signed callback.
5. AverQel verifies scopes and account identity, encrypts the token material, refreshes the safe catalog, and opens the connection inspector.
6. MCP actions remain available only through the current user's approved connection after policy and scope checks pass.

If an OAuth client is not configured, the marketplace entry remains visible but shows Setup pending. This is an operator configuration state, not a request for users to give AverQel their Google or GitHub password.

• Official: reviewed provider operated by the represented vendor.
• Community: reviewed third-party provider; it is never automatically official.
• New: recently added provider within its catalog review period.
• Trending: reviewed popularity signal with explicit review metadata.
• Interactive: reviewed support for interactive workflows.

These are catalog attributes, not security permissions. Approval status controls whether a provider can be connected; badges help users understand provenance and product status.

Remote HTTP means a vendor-hosted HTTPS Streamable HTTP MCP endpoint. Remote SSE means a vendor-hosted HTTPS Server-Sent Events MCP endpoint. AverQel validates remote endpoints and does not let the browser probe them directly.

Stdio, SSH, and local process transports are not supported in this release. AverQel does not clone or execute arbitrary vendor MCP repositories on the VPS. This reduces supply-chain and host-execution risk while the product focuses on approved remote services.

Marketplace previews are reviewed metadata. Once connected, AverQel can refresh the live tool catalog and records a safe catalog revision and health status. Health is an operational signal, not an uptime guarantee, and remote providers can change tools or permissions.

The runtime rejects stale catalogs, disabled providers, revoked connections, removed tools, and policy violations. The frontend receives only typed safe DTOs; provider tokens, client secrets, raw OAuth metadata, and raw MCP event payloads remain server-side.

The vendor owns its MCP implementation, endpoint availability, OAuth application, and tool behavior. AverQel owns the marketplace review, tenant/user connection, encryption, policy, approval, runtime routing, and safe inspection. Keeping those responsibilities separate makes provider updates safer and prevents unreviewed code from running inside AverQel.

• Chat runtimes include OpenRouter, OpenAI-compatible providers, Anthropic, Google, Ollama, LM Studio, and OpenCode Zen.
• Embedding runtimes include local deterministic paths, sentence-transformers, OpenRouter, Ollama, LM Studio, and OpenAI-compatible providers.
• Reranking and web search use their own provider routing and secret boundaries.

These model-provider flows remain separate from the remote MCP marketplace and are not replaced by it.