Before you begin
- Sandbox client credentials from Encrisoft. They are different from any production credentials.
- An installation ID for a sandbox test organisation that contains no customer data.
- The sandbox API and MCP hostnames, provided by Encrisoft.
Sandbox principles
- Sandbox and production use separate client identities. Never reuse a credential across environments.
- Test against a sandbox test organisation only, never against customer data.
- Results are illustrative of behaviour, not of real customer risk or training data.
Smoke test
Run these checks in order. Each should succeed before you move on.
curl -s https://<mcp-host>/healthz
# {"status":"ok"}
curl -s https://<mcp-host>/.well-known/oauth-protected-resource/mcp
curl -s https://<api-host>/.well-known/oauth-authorization-server/oauth
curl -s -o /dev/null -w '%{http_code}\n' -X POST https://<mcp-host>/mcp \
-H 'content-type: application/json' -d '{}'
# 401, with a WWW-Authenticate: Bearer resource_metadata=… headerTOKEN=$(curl -s -u "$CLIENT_ID:$CLIENT_SECRET" https://<api-host>/api/v1/oauth/token \
-d grant_type=client_credentials \
-d resource=https://<mcp-host>/mcp \
-d installation_id="$INSTALLATION_ID" | jq -r .access_token)Then connect your MCP client with the token, list the tools and call each tool in your grant. Confirm that each structuredContent matches the output schema in the Encrisoft MCP Tools Reference.
Negative tests
A robust integration handles each of these without retrying in a loop:
- Token request with a different
resourcevalue: expectinvalid_target. - Token request with an installation ID that is not yours: expect
invalid_grant. - Ask the test organisation’s administrator to revoke the installation, then call a tool: expect a tool error with code
unauthorized. - Call a tool outside your grant: expect code
forbidden. - Call
encrisoft_training_catalogue_v1withpageSize: 26or an unknown argument: expect the call to be rejected by input validation. - Send an expired token: expect HTTP
401and request a new token.
Reporting issues
Send every request with an X-Correlation-Id header. When you report a problem, include the correlation ID, the time (UTC), the tool name and the error code. Never include tokens, client secrets or organisation data in a report.

