# Verify the connection

> Check the endpoint from your own machine before blaming a client.

Before blaming a client, check the endpoint from the same machine. This request is unauthenticated on purpose:

```bash title="Probe the endpoint" icon="terminal"
curl -sS -D - -o /dev/null \
  -X POST https://extensions.copyleaks.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",
       "params":{"protocolVersion":"2025-06-18","capabilities":{},
       "clientInfo":{"name":"probe","version":"1"}}}'
```

A healthy server answers:

```http title="Expected response"
HTTP/2 401
www-authenticate: Bearer resource_metadata=
  "https://extensions.copyleaks.com/.well-known/oauth-protected-resource/mcp"
```

<Check>
  **That 401 is the success case.** It proves the endpoint is reachable, terminating TLS correctly, and advertising its authorization server. A timeout, a 50x, or an HTML error page means the problem is your network, not your config.
</Check>

Follow the chain one step further to see the permissions on offer:

```bash title="Read the protected-resource metadata" icon="terminal"
curl -sS https://extensions.copyleaks.com/.well-known/oauth-protected-resource/mcp | jq .
```

Once connected, ask your agent to check your Copyleaks credit balance. If it answers, you are done.

<Card title="Still not working?" icon="life-ring" href="/mcp/troubleshooting">
  Symptoms, causes and fixes for a connection that will not behave.
</Card>