LABSCO SUMMARY
The product is the governance layer, not the tools.
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.
What it is
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.
What you get
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.
Requirements
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.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Putting every MCP call behind one policy
Register third-party servers into Credal so approvals and access control apply uniformly.
02
Building a server for a team
Assemble connectors, tools and agents into a server scoped to what that team needs.
03
Requiring a human on sensitive actions
Approval enforcement is part of the platform rather than a convention in a prompt.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth (RFC 6750 discovery)
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://app.credal.ai/api/user/[surface]/mcpRequirements
- OAuth (RFC 6750 discovery)