Some vendors give you a token list to prune; Motive's answer is that deleting the connector in the client is the revocation, effective at once. That is fine as long as you know it — there is no second place to check. One implementation detail for client builders: the protected-resource metadata sits at a path suffix rather than the bare well-known URL, so a client that only looks in the standard place will not find it.
Motive's hosted endpoint for their fleet management platform. It appears in Claude as 'Motive Public MCP'. No per-tool list is published, and the endpoint returns 401 to an unauthenticated call.
Access to the Motive platform through the connector. We could not enumerate the tools — the endpoint requires authorisation first.
OAuth 2.0 bearer. Access is revoked by deleting the Motive connector or app in Claude or ChatGPT, which invalidates it immediately.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen