Registering third-party servers into Credal is the tell: the value proposition is that every MCP call — yours or someone else's — passes through one place where access control and approvals are enforced. For an organisation with dozens of connections and a compliance function, that is the problem worth paying to solve. For anyone else there is nothing here to try, since the servers only exist once you have built them.
Credal does not publish one server; it lets an organisation build them. Servers are assembled per organisation from connectors, a pre-built tool library, and agents, and there are several endpoint shapes depending on what you built.
Whatever your organisation assembled. There is a pre-built tool library to draw from, and third-party servers can be registered into the same governance layer.
An enterprise Credal account, sales-led with no public pricing. OAuth with standard discovery. All MCP activity is subject to the platform's access control and approval enforcement, including human-in-the-loop steps.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen