Concepts
Sign-in and consent
How an app asks for access, how you sign in on noiz, and what the app receives.
Connecting an app uses OAuth 2.1, the same standard as "Sign in with" buttons. You prove who you are on noiz, with your noiz session; the app only ever receives a key for the permissions you allowed. It never sees your password, your email address or your two-factor code.
What happens when you connect
The app finds noiz's sign-in
The app calls the server URL without a key and gets a 401 that points to noiz's OAuth metadata. From there it learns where to send you.
Noiz names the app and asks you
The consent page on mcp.noiz.bio shows the app's name and where access will be sent. ChatGPT and Claude identify themselves with a published client document, shown as "Published by" their domain. An app that registered itself is marked "not verified", and an address on your own computer gets a warning. If an app calls itself ChatGPT, Claude or another app noiz knows, but sends access somewhere that app does not, the page warns you and makes Deny the default. The page cannot be shown inside another site.
You sign in on app.noiz.bio
Allowing sends you to app.noiz.bio, signed out or not. If your account has an authenticator, noiz asks for its code every time you connect an app, even on a remembered device: connecting hands out a key. Then noiz names the app and where access goes once more, and asks Connect as @yourname?
The app gets its key
Noiz checks that the same browser started and finished the sign-in, then gives the app a one-time code, which the app trades for its tokens. Cancel on either page and the app is told access was denied.
Discovery, for client developers
POST https://mcp.noiz.bio/mcp
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="OAuth", resource_metadata="https://mcp.noiz.bio/.well-known/oauth-protected-resource/mcp"
GET https://mcp.noiz.bio/.well-known/oauth-protected-resource/mcp
# names the resource and its authorization server, https://mcp.noiz.bio
GET https://mcp.noiz.bio/.well-known/oauth-authorization-server
# the authorize, token and registration endpoints, PKCE S256, CIMD| Requirement | Detail |
|---|---|
| PKCE | Required, S256 only |
| Client identification | Client ID metadata document (CIMD) or dynamic client registration at /oauth/register |
| Resource | Every token is bound to https://mcp.noiz.bio/mcp |
| Scopes | page:read, analytics:read, page:write (see Permissions) |
How long access lasts
Tokens
An access token lasts one hour. The app refreshes it with a refresh token, which changes every time it is used. An app that goes unused for 30 days loses access and has to connect again.
Ending access
Disconnecting the app in your dashboard, under Settings, Security, Connected apps, ends its access at once: its tokens stop working. Deleting your noiz account disconnects every app the same way.
Removing noiz from inside an AI app only makes that app forget its key. To end access for certain, disconnect it in your dashboard.