full:read and full:write is not fine-grained — there is no way to allow reading registrations while forbidding scheduling. But it is a real distinction, declared in discovery metadata where a client can act on it, and it means an analytics assistant does not need write access to answer questions about attendance. Compare with the several servers here whose only scope is 'everything'.
Livestorm's endpoint for their webinar platform. The protected-resource metadata names the server and declares exactly two scopes.
The platform's webinar and session surface. The endpoint requires authorisation before listing, so the tool set comes from their documentation.
OAuth 2.1 with dynamic client registration and PKCE. The scopes are full:read and full:write — coarse, but explicit.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen