1. Open Dashboard → MCP Marketplace and choose an approved provider.
2. Review the publisher, trust status, endpoint, transport, tools, risks, and requested OAuth scopes.
3. Select Connect. The browser goes to the provider's official authorization page.
4. Sign in and approve the requested scopes at Google, GitHub, or another provider.
5. AverQel returns to the connection inspector, captures only safe account identity, refreshes the catalog, and shows the available tools.
6. Configure the connection policy. A connection or scope remains unavailable when it has not been explicitly enabled.
7. Use the protected MCP surface for actions such as searching Gmail or reading a GitHub repository. The runtime checks identity, connection, catalog freshness, tool policy, and approval requirements before calling the remote server.

An Official provider is operated by the vendor represented in the catalog and has been reviewed by AverQel. A Community provider is a reviewed third-party server that is not operated by that official vendor or by AverQel. Community providers never receive the Official badge automatically and always show a trust warning before connection.

Only entries with AverQel's approved trust status can be connected. The catalog is metadata, not a guarantee that a vendor will remain available or that its tools will never change; the runtime still performs ownership, approval, freshness, and catalog checks.

• Official: reviewed vendor-operated provider.
• Community: reviewed third-party provider with a visible warning.
• New: recently published catalog entry within its review window.
• Trending: catalog popularity signal within its review window.
• Interactive: provider reviewed as supporting interactive workflows.
• New, Trending, and Interactive are catalog attributes with review and expiry metadata; they are not hard-coded frontend labels.

AverQel uses provider-specific OAuth profiles, PKCE, signed state, a stable callback, and scope verification. The user authenticates with the provider. AverQel does not receive or store the provider password.

• OAuth transactions, including PKCE state, are encrypted and single-use.
• Access and refresh tokens are encrypted with tenant-bound associated data.
• Safe account identity and verified scope names are stored separately from encrypted credentials.
• Disconnect removes the local token record and requests provider revocation where supported.
• Refresh updates encrypted credentials and verified scope metadata without exposing secrets to the frontend.

DeepSpace applies the most restrictive applicable rule. The effective order is:

1. Connection ownership, provider approval, enabled status, authentication, and catalog freshness.
2. Conversation and DeepSpace scope enablement. Missing or stale overrides are denied.
3. Explicit Blocked tool mode.
4. Allowlist and denylist checks.
5. Read-only mode and the connection risk ceiling.
6. Per-tool mode: Always allow, Needs approval, or Blocked.
7. Platform and tenant safety rules, which Always allow can never bypass.

Always allow permits a tool only after all higher-level checks pass. Needs approval pauses before the remote side effect. Blocked tools are not offered to DeepSpace and cannot be executed through the MCP runtime.

Remote HTTP means AverQel connects over a vendor-hosted HTTPS Streamable HTTP MCP endpoint. Remote SSE means the server uses the Server-Sent Events transport. The endpoint is validated by AverQel before use and the runtime maintains catalog freshness and safe reconnect behavior.

Local stdio processes, SSH-launched servers, arbitrary local servers, and user-supplied executable MCP packages are not supported in this marketplace release. This keeps the VPS from executing unreviewed vendor code and keeps the product focused on remote providers.

Marketplace tool lists are AverQel-reviewed catalog metadata. After authentication, the connection can refresh its live tool catalog, but a remote provider can change tools or availability. AverQel rejects stale catalogs and tools removed from the current catalog.

Health and last-verified indicators are safe status metadata, not a promise of uptime or provider correctness. The browser never performs endpoint health probes or arbitrary metadata discovery. Community logo URLs are validated and fall back to a local identity when unsafe.

AverQel is the secure MCP host/client and policy layer, not a copy of every vendor server. Cloning a vendor repository would create credential, update, licensing, maintenance, and supply-chain responsibilities that belong to the vendor. AverQel instead stores curated public metadata, connects to the official remote endpoint, and enforces its own tenant, user, token, tool, approval, and audit boundaries.

The frontend uses the typed MCP API boundary for marketplace entries, provider details, connections, policies, tools, scoped conversation/DeepSpace controls, refresh, OAuth, and inspection. Responses are explicit DTOs and never include raw server configuration, tokens, client secrets, OAuth transaction data, or raw MCP event payloads.