Troubleshooting¶
Common issues connecting to and using The Coin Daily MCP, and how to resolve them. If something here doesn't fix it, reach out via the contact form or email javad@novaframe.tv.
Connecting¶
The connector won't add. Confirm you're using the exact server URL, including the /mcp path:
A bare https://mcp.thecoindaily.co (no /mcp) won't speak the protocol. The endpoint is HTTPS-only and uses streamable HTTP — plain HTTP and SSE-only clients aren't supported.
Adding the connector sends me to a sign-in page. That's expected. The MCP requires an account, so the first connection runs a standard OAuth flow that takes you to the Coin Daily sign-in page at auth.thecoindaily.co. Sign up or log in, approve access, and the client handles the token from there. See Authentication.
Reconnecting didn't ask me to sign in again. Also expected — the authorization server keeps a short-lived session, so a reconnect can complete silently without re-prompting. To force a fresh sign-in (for example, to test the flow as a new user), reconnect in a private/incognito window or clear cookies for auth.thecoindaily.co.
Signing in¶
I forgot my password. Use the "Forgot your password?" link on the sign-in page to reset it by email.
I never got the confirmation / reset email. Check spam, and allow a minute. Mail is sent from no-reply@thecoindaily.co via Amazon SES. If it still doesn't arrive, contact support.
I want to change or delete my account. Manage everything at mcp.thecoindaily.co/account — including full deletion, which erases your records across our store, Listmonk, and Cognito.
Errors¶
Auth failures return a JSON-RPC error with HTTP 401 and a WWW-Authenticate header pointing at the authorization-server metadata, so a compliant client can start the OAuth flow automatically.
| HTTP | Meaning | Fix |
|---|---|---|
401 |
Missing, invalid, or expired credential | Re-connect (OAuth) or check your API key is sent as Authorization: Bearer tcd_... |
429 |
Rate limit exceeded | Honour the Retry-After header, then retry. Free tier is 60 req/min, 2,000 req/day |
5xx |
Transient server-side issue | Retry with exponential backoff |
Using an API key directly? Make sure the header is exactly Authorization: Bearer tcd_... with no extra whitespace. Lost the key? Replace it from your account page — the old one is revoked atomically.
Tool results¶
A ticker brief comes back found: false. The asset isn't in the publication's tracked universe right now, or there's no active brief for it. Try a major (BTC-USD, ETH-USD, SOL-USD). Ticker arguments are forgiving: btc, BTC, btc-usd, and BTC-USD all resolve to BTC-USD; use the full XXX-USDT form for USDT pairs.
A field I expected is missing or null. This is deliberate. The publication's data-quality system omits a figure rather than substitute a stale or untrustworthy one — for example, derivatives fields are dropped when the upstream feed is stale, and assets not covered by a given source return null instead of a guess. Treat a missing field as "not reliably available," not an error.
search_coverage returns nothing. Broaden the query (it's semantic, so "ETF flows", "spot inflows", and "fund demand" all match related segments), widen the days window, or lower min_relevance. Editorially retracted shows are intentionally excluded.
Numbers look different from another source. Responses include per-metric attribution (provider, endpoint, scope) so you can see exactly what each figure covers — e.g. liquidations are a named-exchange aggregate over a fixed window, which can differ from a public dashboard aggregating more sources or a longer window. Read the attribution block before reconciling.
Still stuck¶
Open the contact form or email javad@novaframe.tv. Include the tool you called, the arguments, and the approximate time (UTC) so we can trace it in the request logs.