Qualification state on October 1, 2026
Direct link| Client or flow | Documented state | Method and limit |
|---|---|---|
| Muse | A user confirmed an earlier connection on September 30. The connection process is documented. | That confirmation is separate from the new consent flow. This qualification has not observed the final native return for a new authorization after the October 1 update. |
| MCP SDK client | Controlled fixture reads on October 1. | In-memory transport and fictitious data; no Muse screen or production OAuth. |
| Isolated OAuth test environment | Authorization, reconnection and revocation checks for the October 1 update. | Real services in an isolated environment; not a consumer assistant. |
| Dot, Hermes and other assistants | Not qualified in this reference. | No dated native trial available here. MCP support does not establish universal compatibility. |
What the documented client flow requires
Direct linkThe remote flow uses Streamable HTTP, OAuth discovery, client registration and authorization code with PKCE S256. The client needs to preserve its connection state, complete the return and discover the tools actually available.
The catalogue depends on account rights and consent permissions. A tool count alone is not a compatibility check. Server version 0.3.0 does not distinguish every change; consult the dated change log (French) as well.
Qualify another assistant
Direct link- Record the client, version or interface, and date.
- Start from its native connection control and authorize one organization with limited reads.
- Check the return, then identity and organization through tool calls.
- Read a known record and compare its fields; check photo access separately.
- Remove access and verify that a fresh read using the former connection is denied.
Record failures by step. An answer retained in conversation history does not prove a new successful tool call. Galerie Auto screen labels remain in French; English documentation does not imply an English product interface.
External operations need their own evidence
Direct linkFacebook Marketplace or Messenger tools do not establish the assistant’s native access to those services, a click, a published listing or a sent message. Preparation, coordination, external execution and CRM synchronization require separate checks.
This reference reports no qualified external publication or send. Newton authorizations and operation-specific evidence remain necessary. The tool catalogue describes their effects; the permissions guide describes access dependencies.
Product documentation reviewed on . Examples are requests to adapt, with no customer data or guaranteed outcome.
Additional sources: