# Check your connection

Distinguish the local CLI, public service health and the authority of an MCP connection.

The local CLI and the remote service identify different parts of a connection. Public health establishes that the service answers; resource access is decided for the actual caller.

## Identify the local command

Print the CLI version and source commit.

```text
lys --version
```



The CLI reports its version and source commit. The remote [plugin connection](/lys/plugin/) uses HTTP and the host's OAuth support; it does not require this local command.

## Read service metadata

**Public health and schema**

```text
GET /api/health
GET /api/openapi.json
```


Health describes the serving directory. OpenAPI describes its declared operations. Neither provides the caller with authority to exercise those operations.

## Discover the connection's authority

**Discover the current connection’s authority**

```json
{"name":"what-can-I-do","arguments":{}}
```


Read the returned resources and actions before selecting a route. A connected-app agent and the person responsible for it are distinct callers. An operation requiring a person session cannot use the agent's connection in its place.

## Answer the refusal

A missing sign-in needs host authentication. A refused signature needs the enrolled agent id and matching key. A missing resource action needs an authorised grant. Preserve an uncertain operation's identifier and reconcile it before attempting another change.