# stensul-health

> Checks credentials, connectivity and available scopes. Run it first when calls fail with authentication or access errors.

Source: https://stensul.com/developers/reference/stensul-health/ · From the live server's tool list, 2026-09-28

- Scope: none
- Access: read

On an instance-URL connection, where sign-in is handled by the host, this tool can report missing client credentials even while data tools work. Use `stensul-check-auth` to confirm the session instead.

## Inputs

None.

## Example request

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "stensul-health",
    "arguments": {}
  }
}
```

## Response

A checklist: whether credentials are configured, whether a token was obtained, which scopes the connection has, and whether the API is reachable.

## Errors

| Status | Message | Cause | Fix |
| --- | --- | --- | --- |
| 401 | Authentication expired or missing | The session's authorization expired. | Sign in again when the host prompts. On a 401 or 403, the server's instructions tell the model to re-check sign-in first. |