Overview
check_connection performs connectivity diagnostics:
- API reachability — verifies Stobo API server is responding
- Configuration check — validates your base URL and API key presence
- Network diagnostics — identifies connection issues
- Health status — confirms API is operational
This tool is completely free and works without an API key.
Parameters
This tool takes no parameters.Example prompts
Response structure
The tool returns a JSON object with:Connection status: “ok”, “error”, “timeout”, or “connection_refused”
The API base URL being used (from STOBO_BASE_URL env var)
Whether an API key is configured (doesn’t validate it, just checks presence)
HTTP status code from health endpoint (200 = success)
Error message if connection failed
Suggested fix for the issue (if applicable)
Usage example
Status codes
| Status | Meaning | Action |
|---|---|---|
ok | API is reachable and responding | No action needed |
error | API returned non-200 status | Check API status or try again |
timeout | Request took too long (>10s) | Check network or retry |
connection_refused | Cannot reach API server | Check internet, firewall, or API status |
When to use
Usecheck_connection when:
- Tools are failing unexpectedly — verify it’s not a connectivity issue
- First-time setup — confirm configuration is correct
- After changing STOBO_BASE_URL — verify custom endpoint works
- Network issues suspected — isolate whether problem is local or API-side
Common issues and fixes
status: connection_refused
status: connection_refused
The API server is not reachable.Possible causes:
- No internet connection
- Firewall blocking outbound HTTPS
- VPN or proxy interfering
- API server is down (rare)
- Check your internet connection
- Try from a different network
- Disable VPN temporarily
- Check Stobo status page
status: timeout
status: timeout
The API is slow to respond or unreachable.Possible causes:
- Slow network connection
- API server is overloaded (rare)
- DNS issues
- Try again in a few seconds
- Check your network speed
- Try from a different network
status: error, http_code: 404
status: error, http_code: 404
The health endpoint doesn’t exist.Possible causes:
- Wrong STOBO_BASE_URL configured
- Typo in base URL
- Remove STOBO_BASE_URL env var (use default)
- If using custom URL, verify it’s correct
status: ok, has_api_key: false
status: ok, has_api_key: false
Connection works but no API key configured.Impact:
- Free tools work fine
- Paid tools will fail with auth errors
- If using paid tools, add STOBO_API_KEY to your MCP config
- If only using free tools, no action needed
Configuration check
The tool reports your current configuration:- Using default API endpoint (recommended)
- API key is configured
- API server is healthy
Next steps
If connection check passes:- Proceed with using other tools normally
- If tools still fail, the issue is likely API key or credits
- See troubleshooting guide
- Check environment variables