Probe Helpcenter
Auto Light Dark
Auto Light Dark

/mcp shows probe or trace as failed

Problem

In Claude Code, /mcp lists probe or trace as failed or disconnected. In another assistant, the Probe tools are missing or return an authorisation error.

Solution

  1. Check that your server is up. Open your welcome page, https://<your-company>.trial.esharp.se/. If it doesn't load, contact us.

  2. Check your key. A key works for 14 days, and creating a new key stops the old one at once. If in doubt, press Create a new key on the welcome page, then run claude mcp remove probe and claude mcp remove trace and add the new commands. In another assistant, replace the header value in your configuration.

  3. Check the addresses. Run claude mcp list. The addresses should be https://probe.<your-company>.trial.esharp.se/mcp and https://trace.<your-company>.trial.esharp.se/mcp. In another assistant, also check that the key is sent in the header X-Esharp-Access.

  4. Check your company network. If the welcome page loads in your browser but your assistant can't connect, a proxy or firewall may block it. Ask your IT department to allow outbound HTTPS to probe.<your-company>.trial.esharp.se and trace.<your-company>.trial.esharp.se.

  5. Restart your assistant and try again.