This is what the protocol's discovery layer is for: with no vendor guide at all, a compliant client can still find the authorisation server, request the right scope and connect. That it works is a point in the registry's favour. It also means you are connecting to something whose surface you cannot inspect beforehand, and with enterprise demo-led sales there is no free tier to try it on. Worth knowing before it goes into a plan.
Conveo's endpoint for their qualitative research platform — designing studies, analysing interviews, generating insight. It is registered in the official MCP registry as ai.conveo/conveo v1.0.1 over streamable HTTP.
Conveo publishes no MCP documentation of its own; the homepage shows only an 'Open platform MCP API' label in a product graphic. The endpoint requires OAuth, so the tools could not be listed.
A Conveo account. The client discovers the authorisation server automatically from the protected-resource metadata and requests scope mcp:tools.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen