SellerX · OAuth Scopes

SellerX OAuth Scopes

OAuth 2.0 searched

SellerX publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the SellerX API on a user’s behalf.

Tokens are issued from https://mcp.sellerx.com/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.

CompanyE-CommerceConsumer BrandsRetailAmazon AggregatorMarketplace-SellerConsumer Packaged GoodsGermany

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://mcp.sellerx.com/authorize

Token URL
https://mcp.sellerx.com/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
read	Advertised in scopes_supported by both the authorization-server metadata and the protected-resource metadata for https://mcp.sellerx.com/mcp. SellerX publishes no definition of what this scope grants.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-05'
method: searched
source: https://mcp.sellerx.com/.well-known/oauth-authorization-server
docs: null
note: >-
  Not derived from OpenAPI — SellerX publishes none. These scopes are read
  verbatim from scopes_supported in the RFC 8414 authorization-server metadata
  and the RFC 9728 protected-resource metadata served by the SellerX MCP host.
  SellerX publishes no scopes/permissions reference page, so no description
  beyond the scope string itself exists publicly. Nothing is inferred.

schemes:
- name: OAuth2
  source: well-known/sellerx-oauth-authorization-server.json
  issuer: https://mcp.sellerx.com/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mcp.sellerx.com/authorize
    tokenUrl: https://mcp.sellerx.com/token

scopes:
- scope: read
  description: >-
    Advertised in scopes_supported by both the authorization-server metadata and
    the protected-resource metadata for https://mcp.sellerx.com/mcp. SellerX
    publishes no definition of what this scope grants.
  flows: [authorizationCode]
  sources:
  - well-known/sellerx-oauth-authorization-server.json
  - well-known/sellerx-oauth-protected-resource.json

resources:
- resource: https://mcp.sellerx.com/mcp
  authorization_servers: [https://mcp.sellerx.com/]
  scopes_supported: [read]

x-evidence:
  fetched: '2026-08-05'
  probed:
  - url: https://mcp.sellerx.com/.well-known/oauth-authorization-server
    http_status: 200
  - url: https://mcp.sellerx.com/.well-known/oauth-protected-resource/mcp
    http_status: 200

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/sellerx-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.