Verify the connection

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

Probe the endpoint

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:

Expected response

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

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.

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

Read the protected-resource metadata

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.

Still not working?

Symptoms, causes and fixes for a connection that will not behave.

Get started

Connecting

Using it

Help

Still not working?