An endpoint named provisioning is one that creates and destroys infrastructure. CloudX does the protocol part properly — a 401 that tells the client where to authenticate is what lets a connection configure itself — but the operational question is scoping, and that is worth reading their tools page for before an agent has a token. Their examples page exists; use it.
CloudX's provisioning endpoint. The address itself says what it does — this is infrastructure provisioning rather than a read-only API.
17 tools by the vendor's documentation, with a dedicated tools page and worked examples. The endpoint returns 401 with discovery metadata rather than listing anything anonymously.
OAuth 2.1 bearer. An unauthenticated initialize returns 401 with WWW-Authenticate resource metadata, which is the correct behaviour and makes client auto-configuration possible.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen