6Sense Insights · OAuth Scopes

6Sense Insights OAuth Scopes

OAuth 2.0 probed

6Sense Insights uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyABMAccount-Based MarketingIntent DataB2BPredictive AnalyticsRevenueSales IntelligenceMarketing TechnologyAIData Enrichment
Scopes: 0 Flows: Method: probed

Scopes (0)

6Sense Insights implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://support.6sense.com/docs/6sense-model-context-protocol-mcp-1

Source

OAuth Scopes

6sense-insights-scopes.yml Raw ↑ 
generated: '2026-08-13'
method: probed
source: >-
  https://api.6sense.com/.well-known/oauth-authorization-server and
  https://api.6sense.com/.well-known/oauth-protected-resource/mcp (both fetched
  live, HTTP 200).
description: >-
  6sense's OAuth surface publishes exactly one scope. It governs the MCP server
  at https://api.6sense.com/mcp, not the REST APIs — those authenticate with an
  `Authorization: Token <api_token>` header and have no OAuth scopes. What the
  REST APIs scope instead is the API TOKEN itself: tokens are issued per API
  group and are limited by the credit type the customer purchased, and the
  Score and Segments settings on a token further restrict what detail it may
  return. That authorization model is not expressed as OAuth scopes anywhere
  6sense publishes.
docs: https://support.6sense.com/docs/6sense-model-context-protocol-mcp-1
authorization_server: >-
  https://auth.6sense.com/v1/apps/agentic/P32lusHUPY06hG8MJtqJnKEmq7hJ/MS3CTIZ4l7VZ4pFeraAIy18Y6wIVN
resource: https://api.6sense.com/mcp
scopes:
  - name: mcp:use
    description: >-
      Read-only access to 6sense data through the 6sense MCP server, scoped to
      the 6sense instance and the user account used during authorization.
    resource: https://api.6sense.com/mcp
    grants: read
    evidence: >-
      scopes_supported ["mcp:use"] in both the RFC 8414 authorization-server
      metadata and the RFC 9728 protected-resource metadata.
scope_count: 1
notes:
  - >-
    Authorization is per user — every 6sense user must complete the consent flow
    individually, and a connector is isolated to the instance authorized during
    that flow.
  - >-
    The scope is coarse: there is no per-capability decomposition, so a client
    granted mcp:use reaches every documented MCP capability the user's own
    6sense entitlements allow. Entitlement, not scope, is the real boundary.
  - >-
    No token-scope / permission reference page is published for the REST API
    tokens; the docs describe API groups and credit types in prose only.