Documentation

View as Markdown

Troubleshooting Tariff Code Compliance connections

Use this guide when Tariff Code Compliance will not connect, open sign-in, or complete a request from Claude, ChatGPT, or another MCP client.

Start here

  1. Confirm that your client is using the exact production MCP endpoint:
https://api.prod.tariffcodecompliance.com/tariff-code-compliance/v1/mcp
  1. Remove an older Tariff Code Compliance connection before recreating it. This is the usual fix for invalid_client errors from an outdated connection.
  2. Retry in a normal browser window and allow pop-ups for your client and Auth0 so sign-in and consent can finish.
  3. Never paste an access token, password, or other credential into a chat or support request.

Claude

  • You cannot find connector settings: from Claude's home screen, choose Customize, then Connectors.
  • The connector is unavailable in a Team or Enterprise workspace: ask an Owner or Primary Owner to add or enable it for the workspace.
  • A Free account cannot add another custom connector: Anthropic currently limits Free accounts to one custom connector. Remove the unused connector or use the official Tariff Code Compliance connector.

Return to Tariff Code Compliance for Claude for the illustrated setup paths.

ChatGPT

  • Developer mode or Create app is unavailable: check your plan, workspace role, and administrator policy in OpenAI's developer mode and MCP apps guide.
  • The app does not open sign-in: confirm the endpoint above, then remove and recreate the custom MCP app.

Return to Tariff Code Compliance for ChatGPT for the illustrated setup path.

MCP clients and cURL

  • OAuth does not open: confirm that the endpoint is exact and that the client supports remote Streamable HTTP OAuth connectors.
  • A request returns HTTP 400: confirm that Mcp-Method matches the JSON-RPC method and that Mcp-Name matches params.name for tools/call.
  • A request returns HTTP 401 or 403: reconnect through OAuth instead of reusing an expired token, and confirm that the grant includes tcc.knowledge_graph.read and the current Tariff Code Compliance Explorer MCP entitlement.

Return to Tariff Code Compliance Explorer with MCP for endpoint, protocol, discovery, and cURL details.

Still need help

If your issue is not described here, contact support. Include the client you are using, the step that failed, and the visible error message. Do not include passwords, tokens, or other credentials.