# stensul-check-auth

> Reports whether the current session has a valid sign-in, where the token came from, and what to do next.

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

- Scope: none
- Access: read

Most hosts handle sign-in for you. When you connect through your instance URL (`https://mcp.stensul.com/<your-instance>/mcp`), the host sends the token with every request and this tool always reports `source: "http-bearer"`.

## Inputs

None.

## Example request

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

## Response

```json
{
  "hasToken": true,
  "source": "http-bearer",
  "baseUrl": "https://<your-instance>.stensul.com",
  "tenant": "<your-instance>",
  "expiresAt": null,
  "secondsRemaining": null,
  "nextStep": "Authenticated via HTTP bearer. You can call data tools now."
}
```

Captured from a Stensul-internal tenant on 2026-09-28. Instance name replaced with a placeholder.

## 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. |