Glossary

HTTPS

HTTPS is HTTP over TLS, so traffic is encrypted. OneLifeVibe requires HTTPS on port 443 for webhook endpoints and serves both MCP connectors over HTTPS.

Updated November 15, 2026

Standard
RFC 9110 (HTTP Semantics)
Also called
HTTP over TLS

At OneLifeVibe

Related terms

What it means

HTTPS is HTTP carried over TLS, so the request and response traffic is encrypted. The HTTP parts do not change: methods, headers, status codes and bodies keep their usual meaning. RFC 9110 covers HTTP semantics, while TLS handles encryption and certificate-based server authentication.

In practice, an https URL tells the client to establish a TLS session before it sends the HTTP request. That is the difference from an http URL, where the request and response travel in plain text.

How it works

The client connects to the host, usually on port 443, and performs a TLS handshake. During the handshake it checks the server certificate against the hostname and a trusted certificate chain. If that check fails, the connection should fail before any HTTP request is sent.

The two sides then derive session keys and encrypt application data. The client sends the same HTTP request it would send over plain HTTP, but the bytes on the wire are protected. Redirects from http to https are still useful, but the first request to the http URL was not encrypted.

How OneLifeVibe uses it

OneLifeVibe webhook endpoints must be https on port 443 on a public hostname. The platform also runs two MCP servers over HTTPS: the account connector at https://onelifevibe.com/mcp, which needs the person's OneLifeVibe sign-in, and the free connector at https://onelifevibe.com/mcp/free, which needs no sign-in and is read-only. The free connector is stateless, so any MCP client that supports remote servers can add https://onelifevibe.com/mcp/free as a custom connector.

MCP messages to https://onelifevibe.com/mcp are JSON-RPC 2.0 over POST. A tools/call request names the tool, for example olv_list_worlds, and passes an arguments object. The account connector uses OAuth 2.1 authorization code with PKCE (S256). The authorization server issuer is https://accounts.onelifevibe.com/realms/olv, a Keycloak identity provider.

Tokens for the OneLifeVibe connector are always addressed to https://onelifevibe.com/mcp. MCP clients may send resource=https://onelifevibe.com/mcp, but the token audience stays the same whether or not the parameter is sent. Access tokens last 5 minutes.

Common mistakes

A webhook endpoint on http, a port other than 443 or a private hostname does not meet the stated requirement. Check the full URL before you register it.

With MCP, check which connector you are adding. The free, read-only connector is https://onelifevibe.com/mcp/free; the account connector is https://onelifevibe.com/mcp. The resource parameter does not change the token audience.

Questions

What URL should an MCP client use for the OneLifeVibe account connector?

Use https://onelifevibe.com/mcp. It requires the person's OneLifeVibe sign-in and uses OAuth 2.1 authorization code with PKCE (S256) with issuer https://accounts.onelifevibe.com/realms/olv.

Do OneLifeVibe webhook endpoints have to use HTTPS on port 443?

Yes. Webhook endpoints must be https on port 443 on a public hostname.

See it working. The OneLifeVibe connector and Platform API put these pieces together.

Get a free key Read the docs

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.