Sequans Authentication

generated: '2026-09-16'
method: probed
source: https://sequans.com/.well-known/oauth-authorization-server + https://sequans.com/wp-json/
docs: null
description: >-
  Sequans publishes no developer program and no authentication documentation. This profile was
  read from the live sequans.com surface: the RFC 8414 / RFC 9728 metadata served by the WordPress
  MCP Adapter describes the MCP server's authorization model, and the WordPress REST index lists no
  authentication methods of its own (its `authentication` block is empty). Product documentation,
  SDKs and firmware sit behind the my.sequans.com support-zone account, which is a customer web
  login, not an API credential.
summary:
  types: [oauth2]
  anonymous_read: false
  api_key_in: []
  oauth2_flows: [authorizationCode]
schemes:
- name: SequansMCPOAuth
  type: oauth2
  applies_to: https://sequans.com/wp-json/mcp/mcp-oauth-server
  description: >-
    OAuth 2.1 authorization code with PKCE (S256) for the remote MCP server. Public clients
    (token_endpoint_auth_method none), refresh tokens supported, client ID metadata documents
    supported, single `mcp` scope, bearer token in the Authorization header. An unauthenticated
    call returns 401 with an RFC 9728 challenge naming the protected-resource metadata document.
  issuer: https://sequans.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://sequans.com/oauth/authorize
    tokenUrl: https://sequans.com/oauth/token
    revocationUrl: https://sequans.com/oauth/revoke
    scopes: 1
  detail: scopes/sequans-scopes.yml
  sources: [https://sequans.com/.well-known/oauth-authorization-server, https://sequans.com/.well-known/oauth-protected-resource]
- name: WordPressSession
  type: other
  applies_to: https://sequans.com/wp-json/mcp/mcp-adapter-default-server
  description: >-
    The default MCP adapter server answers anonymous calls with 401 rest_forbidden and no OAuth
    challenge, meaning it is gated by WordPress user capabilities (a logged-in site user) rather
    than by the OAuth server above.
  sources: [https://sequans.com/wp-json/mcp/mcp-adapter-default-server]
not_found:
  api_keys: No API key programme, developer portal or key-issuance flow exists on any Sequans host.
  openid_connect: https://sequans.com/.well-known/openid-configuration returns 404.
  mutual_tls: Not advertised.
  dynamic_client_registration: No RFC 7591 registration_endpoint is advertised.
x-evidence:
  fetched: '2026-09-16'
  probes:
  - url: https://sequans.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://sequans.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://sequans.com/.well-known/openid-configuration
    status: 404
  - url: https://sequans.com/wp-json/
    status: 200
  - url: https://sequans.com/wp-json/mcp/mcp-oauth-server
    status: 401
  - url: https://sequans.com/wp-json/mcp/mcp-adapter-default-server
    status: 401