Crayon · Authentication Profile

Crayon Authentication

Authentication

Crayon secures its APIs with oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

Competitive IntelligenceMarket IntelligenceSales EnablementBattlecardsWin-Loss AnalysisProduct MarketingArtificial IntelligenceMCP

Methods: oauth2 Schemes: 2 OAuth flows: authorizationCode API key in:

Security Schemes

CrayonOAuth2 oauth2

· flows: authorizationCode

BearerToken http

scheme: bearer

Source

Authentication Profile

generated: '2026-08-14'
method: probed
source: https://mcp.crayon.co/.well-known/oauth-authorization-server
docs: null
note: >-
  Crayon publishes no developer portal, API reference or auth guide. This profile is read entirely
  from the machine-readable OAuth metadata the MCP host and app host serve anonymously (RFC 8414 +
  RFC 9728) and from the 401 challenge the MCP endpoint returns. The earlier version of this file
  was derived from a spec belonging to Crayon Group ASA (crayon.com) and has been quarantined —
  see _wrong-company/README.md.

summary:
  types:
  - oauth2
  api_key_in: []
  oauth2_flows:
  - authorizationCode
  bearer: true
  dynamic_client_registration: true
  pkce_required_methods:
  - S256

schemes:
- name: CrayonOAuth2
  type: oauth2
  applies_to: https://mcp.crayon.co/mcp/
  flows:
  - flow: authorizationCode
    issuer: https://app.crayon.co
    authorizationUrl: https://app.crayon.co/oauth/authorize/
    tokenUrl: https://app.crayon.co/oauth/token/
    revocationUrl: https://app.crayon.co/oauth/revoke_token/
    registrationUrl: https://app.crayon.co/oauth/register/
    refresh_supported: true
    scopes:
      mcp:read: Read access to the Crayon competitive-intelligence MCP server
  token_endpoint_auth_methods_supported:
  - client_secret_post
  - client_secret_basic
  - none
  code_challenge_methods_supported:
  - S256
  sources:
  - well-known/crayon-oauth-authorization-server.json
  - well-known/crayon-oauth-protected-resource.json
- name: BearerToken
  type: http
  scheme: bearer
  applies_to: https://mcp.crayon.co/mcp/
  note: >-
    The protected-resource metadata declares bearer_methods_supported ["header"], and an
    unauthenticated POST returns WWW-Authenticate: Bearer error="invalid_token". The access token
    is carried in the Authorization header.
  sources:
  - well-known/crayon-oauth-protected-resource.json

not_documented:
- >-
  The Content API and Answers API that Crayon markets have no published authentication model —
  no key format, no header name, no token endpoint appears on any public page.

x-evidence:
- fetched: '2026-08-14'
  url: https://mcp.crayon.co/.well-known/oauth-authorization-server
  http_status: 200
- fetched: '2026-08-14'
  url: https://mcp.crayon.co/.well-known/oauth-protected-resource/mcp/
  http_status: 200
- fetched: '2026-08-14'
  url: https://app.crayon.co/.well-known/oauth-authorization-server
  http_status: 200
- fetched: '2026-08-14'
  url: https://mcp.crayon.co/mcp/
  http_status: 401