# Troubleshooting

> Common issues and fixes for MCP Bond.

:::tip[Quick tip]
Most of what lands on this page clears the same way: **remove the Valency connector, then add it back.** It takes about two minutes, and you won't lose anything: your account, history, and settings live on our side. [Steps for your platform](https://docs.valency.io/help/reconnecting.md).
:::

Still stuck? Run through the quick checks and common fixes below before reporting an issue.

## Quick checks

1. **Server status**: Check [mcp.valency.io/health](https://mcp.valency.io/health). If it's down, the server is the problem.
2. **Connector URL**: Confirm the server URL is `https://mcp.valency.io/`.

## Common issues

### "Couldn't reach the MCP server" in Claude

Usually the MCP server URL is wrong. Confirm the connector points at `https://mcp.valency.io/`. See the [Claude setup guide](https://docs.valency.io/guides/claude.md) for the full walkthrough. If the URL is correct but Valency used to work and just stopped, see [Did Valency stop working recently?](#did-valency-stop-working-recently) below.

### Did Valency stop working recently?

We recently upgraded how Valency signs you in. If your connector was set up before the change, what you see depends on the platform:

- **ChatGPT** shows a screen titled **"Add Valency again"** during sign-in. The old connector can't be revived; remove it and add a fresh one.
- **Claude and CLI connectors** may ask you to sign in to Valency again out of the blue. That's expected, once. Complete the sign-in and you're back. If sign-in loops or keeps failing, remove and re-add the connector.

**Fix:** See [Reconnecting to Valency](https://docs.valency.io/help/reconnecting.md) for the two-minute, per-platform steps.

### Claude says "Authorization with Valency failed"

After signing in, Claude sometimes reports:

> Authorization with Valency failed. You can check your credentials and permissions. If this persists, share this reference with support: "ofid_…"

Despite the wording, your credentials are usually fine. First check which email you signed in with: in most cases it isn't the email your Valency account is under. Sign in again with the right email, or check your account at [app.valency.io](https://app.valency.io/).

If you're confident the email is right, [remove and re-add the connector](https://docs.valency.io/help/reconnecting.md). If it still fails after that, [contact us](https://docs.valency.io/help/reporting-issues.md) and include the **email you signed in with**. The `ofid_` reference is generated by Claude, not by Valency, so we can't look it up on our side.

<a id="sign-in-fails-with-redirect_uri-is-not-registered"></a>
<a id="the-callback-port-is-already-in-use"></a>
<a id="oauth-callback-port-is-already-in-use"></a>

### Older instructions mention pinning a callback port

Earlier versions of the [Claude Code](https://docs.valency.io/guides/claude.md#using-it-in-claude-code) and [Codex CLI](https://docs.valency.io/guides/chatgpt/codex-cli.md) guides pinned a local sign-in port (`--callback-port 33418` / `mcp_oauth_callback_port=33418`) because Valency only accepted redirects on a fixed list of local ports. That restriction is gone: sign-in now works on whatever port your client picks, and the errors pinning used to work around (`redirect_uri is not registered`, the callback port being in use) no longer apply.

There's nothing to change: the pin is harmless where it's already set. If sign-in fails anyway, remove and re-add the connector without the port setting. See [Reconnecting to Valency](https://docs.valency.io/help/reconnecting.md).

### Sign-in doesn't work

- Signed in fine, but Claude then reported an authorization failure? See ["Authorization with Valency failed"](#claude-says-authorization-with-valency-failed) above
- Codex CLI says "Authorization server response missing required issuer"? Update Codex to 0.147.0 or later. See [Codex CLI troubleshooting](https://docs.valency.io/guides/chatgpt/codex-cli.md#codex-version)
- Try a different browser or clear cookies

### No tools appear

- Refresh the page or restart the app
- Check that the MCP server URL is correct: `https://mcp.valency.io/`

### No results returned

- The server may be temporarily down; check [mcp.valency.io/health](https://mcp.valency.io/health)
- Try a simpler search query

### Nothing works at all

Start with the server health check at [mcp.valency.io/health](https://mcp.valency.io/health). If that's down, the server is the problem. [Report it immediately](https://docs.valency.io/help/reporting-issues.md).

## Still stuck?

See [Reporting Issues](https://docs.valency.io/help/reporting-issues.md) for how to get help.