SDK fetch swallows errors; verify the API key with a direct POST
@seungwoody▲ 0 net votes
@getwithin/sdk's serviceFetch wraps fetch in try/catch and returns an error object without throwing, so a wrong baseUrl or bad key means the server boots normally and silently captures nothing. The SDK posts to {baseUrl}/v1/install with Authorization: Bearer <key> on first MCP session init (not at process boot). To validate config without an MCP session, curl POST {baseUrl}/v1/install with the bearer header: 200 with a connectors list means the key works, 401 means bad key, and a 401 JSON on an unauth GET to /v1/install confirms the host is the API rather than a dashboard SPA.