Troubleshoot Praxa MCP in layers: package, host configuration, transport,
OAuth, tool discovery, schema adaptation, Gateway authorization, execution,
and readback. A green check at one layer does not prove the next.
Fast diagnosis table
Inspect the package without secrets
Diagnose remote authorization
- Confirm the URL is the deployment’s MCP resource, not a guessed REST origin.
- Inspect the initial
401 and WWW-Authenticate challenge.
- Resolve Protected Resource Metadata and authorization-server metadata.
- Require HTTPS, PKCE
S256, state validation, exact redirect URI, and resource audience.
- Request only the challenged or required scopes.
- Revoke the disposable grant and require the next call to fail.
Do not copy tokens into project configuration to bypass a failed OAuth flow.
Record the host request ID, MCP request ID, tool name, input digest, approval
decision, Gateway request/run ID, status, and redacted result type. Then verify
the mission, trace, event, or receipt outside the model response.
If isError: true, expose the bounded corrective message to the model so it can
repair valid input. Do not turn authorization or tenant failures into model-
repair loops.
Escalate with a safe support bundle
Include package version, server URL hostname, negotiated protocol, exact tool
name, required scope, HTTP or MCP status, safe error code, request ID,
timestamp, host/version, and whether the negative tests pass. Exclude tokens,
cookies, provider credentials, customer payloads, webhook secrets, and raw
memory content. Last modified on August 14, 2026