Mud\Wtr · OAuth Scopes

Mud\Wtr OAuth Scopes

OAuth 2.0 probed

Mud\Wtr publishes 4 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Mud\Wtr API on a user’s behalf.

Tokens are issued from https://account.mudwtr.com/authentication/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyCommerceE-CommerceRetailConsumer GoodsFood and BeverageShopifyAgentic CommerceMCPGraphQLUniversal Commerce Protocol

Scopes: 4 Flows: Method: probed

OAuth endpoints

Authorization URL
https://account.mudwtr.com/authentication/oauth/authorize

Token URL
https://account.mudwtr.com/authentication/oauth/token

Flows

Scopes (4)

Scope	Description	Flows
openid	Standard OpenID Connect scope; requests an ID token identifying the customer.
email	Releases the customer's email and email_verified claims.
customer-account-api:full	Full access to the Customer Account API on behalf of the signed-in customer.
customer-account-mcp-api:full	Full access to the Customer Account MCP API on behalf of the signed-in customer. No anonymous customer-account MCP endpoint was found on mudwtr.com; /customer/api/mcp returned 404.

📄 Provider scope reference: https://shopify.dev/docs/api/customer

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: https://mudwtr.com/.well-known/oauth-authorization-server
docs: https://shopify.dev/docs/api/customer
description: >-
  OAuth scopes advertised by the authorization server MUD\WTR's own host points at. There is no
  OpenAPI with oauth2 securitySchemes to derive from; these values are read verbatim from the
  scopes_supported array of the discovery document.
authorization_server: https://shopify.com/authentication/13794345014
authorization_endpoint: https://account.mudwtr.com/authentication/oauth/authorize
token_endpoint: https://account.mudwtr.com/authentication/oauth/token
scope_count: 4
scopes:
- name: openid
  description: Standard OpenID Connect scope; requests an ID token identifying the customer.
  category: identity
- name: email
  description: Releases the customer's email and email_verified claims.
  category: identity
- name: customer-account-api:full
  description: Full access to the Customer Account API on behalf of the signed-in customer.
  category: account
- name: customer-account-mcp-api:full
  description: >-
    Full access to the Customer Account MCP API on behalf of the signed-in customer. No anonymous
    customer-account MCP endpoint was found on mudwtr.com; /customer/api/mcp returned 404.
  category: agent
notes:
- Scopes are Shopify customer-account scopes bound to this shop, not MUD\WTR-authored scopes.
- The Storefront GraphQL API and the /api/mcp storefront MCP server require no scope at all.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/mud-wtr-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.