Caller Identification
MCPServerCallerIdentified
The Hopex identity of a caller has been resolved. This event is emitted:
- the first time a caller is seen;
- again every 30 minutes while the caller remains active (the identity is cached for 30 minutes, and activity does not extend this period);
- whenever the caller switches schema or client installation.
It is not a session count, and there is no matching end event. A connection that never authenticates successfully produces no event.
Context (JSON) | Comment |
|---|---|
mcpCorrelationId | Identifier of the caller (see Correlation Identifier) |
clientName | Name declared by the AI client application (e.g. claude-ai (via mcp-remote 0.1.37), mcp-inspector); Unknown when not available (see note below) |
clientVersion | Version declared by the AI client; Unknown when not available |
userAgent | HTTP User-Agent header of the request, truncated to 128 characters. Indicative only: often the default value of an HTTP library (e.g. node). Absent when the header is empty |
schema | Hopex GraphQL schema used by the caller |
allowMutations | true if write operations are enabled for this caller; false for read-only |
authMode | Authentication mode: OAuth or ApiKey |
repository | Name of the Hopex repository the user is connected to |
login | Hopex login name of the user |
person | Full name of the user |
profile | Hopex profile assigned to the user |
identityProvider | External identity provider used to sign in. Present only when the user signed in through an external identity provider; absent for a local UAS login or an API key |
Note on Unknown client names. Clients using MCP protocol revisions up to 2025-11-25 declare their name and version only once, when they connect. The server remembers them per caller when that connection is authenticated: with OAuth, or with an API key when authentication is required upfront (default configuration). When lazy authentication is enabled, the connection is anonymous and clientName / clientVersion may remain Unknown; userAgent is then the only hint. Clients using the 2026-07-28 revision normally send their name with every request, but the protocol leaves it optional.