To stop using an Oddswire MCP connection, disconnect it in the host application and revoke its authorization through the Oddswire Clerk account flow.
Understand token expiry
Previously issued signed access tokens can remain valid until expiry. Disconnecting a host is not proof that every issued token has immediately expired.
Account controls still apply
Oddswire rechecks current membership, account/key status and source reviews for data delivery. Removing workspace membership, disabling the local user or revoking the workspace’s active key blocks subsequent requests that depend on that authority. Those actions can affect other integrations too.
Creating a replacement active key can allow an otherwise valid OAuth connection again. To withdraw consent, revoke the connector authorization itself rather than relying only on key rotation.
If you used an API-key host
Remove the stored credential from the host’s private configuration and revoke or rotate it if it may have been exposed. Never paste it into a chat message to disconnect a connector.
See MCP connection and revocation details. Contact support with the host name and redacted error/reference, without sharing tokens or secrets.