Mutiny HQ · Authentication Profile

Mutiny Hq Authentication

Authentication

Mutiny HQ secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyGo-To-MarketSales EnablementMarketingWebsite PersonalizationArtificial IntelligenceAgentsMCPAccount Based MarketingContent Generation

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

Security Schemes

OAuth2 oauth2

scheme: authorizationCode

Source

Authentication Profile

generated: '2026-08-13'
method: searched
source: https://mcp.mutinyhq.com/.well-known/oauth-authorization-server
docs: https://help.mutinyhq.com/articles/2908744000-mutiny-model-context-protocol-mcp
docs_additional:
- https://help.mutinyhq.com/articles/5255538544-mcp-data-handling-security
- https://help.mutinyhq.com/articles/6009433418-setting-up-sso-on-your-saml-idp
summary:
  types: [oauth2]
  oauth2_flows: [authorizationCode]
  pkce: [S256]
  dynamic_client_registration: true
schemes:
- name: OAuth2
  type: oauth2
  scheme: authorizationCode
  authorizationUrl: https://mcp.mutinyhq.com/oauth/authorize
  tokenUrl: https://mcp.mutinyhq.com/oauth/token
  registrationUrl: https://mcp.mutinyhq.com/oauth/register
  code_challenge_methods: [S256]
  token_endpoint_auth_methods: [client_secret_post, none]
  scopes:
  - read_asset_groups
  - create_asset_groups
  - publish_asset_groups
  - read_library_content
  - manage_library_content
  sources: [well-known/mutiny-hq-oauth-authorization-server.json]
protected_resource:
  metadata: well-known/mutiny-hq-oauth-protected-resource.json
  resource: https://mcp.mutinyhq.com
  authorization_servers: [https://mcp.mutinyhq.com]
challenge:
  probed: '2026-08-13'
  request: POST https://mcp.mutinyhq.com/mcp with a JSON-RPC tools/list body and no token
  http_status: 401
  body: '{"jsonrpc":"2.0","error":{"code":-32001,"message":"Authentication failed."},"id":null}'
  www_authenticate: null
  gap: >-
    The 401 carries no WWW-Authenticate header, so a client cannot discover the
    RFC 9728 protected-resource metadata from the challenge itself — the metadata URL
    has to be known out of band. Everything else in the OAuth chain (metadata, PKCE,
    dynamic registration) is correctly published.
sso:
  saml: true
  plan: Enterprise
  docs: https://help.mutinyhq.com/articles/6009433418-setting-up-sso-on-your-saml-idp
token_handling:
  transport_security: HTTPS (TLS 1.2+)
  revocable: Tokens are scoped to specific permissions and can be revoked at any time.
  password_sharing: Mutiny states a user's password is never shared with the AI assistant.
  source: https://help.mutinyhq.com/articles/5255538544-mcp-data-handling-security
notes: >-
  Mutiny's public programmatic surface is its hosted MCP server, protected by
  OAuth 2.0 authorization-code flow with PKCE (S256) and RFC 7591 dynamic client
  registration. Product/CRM integrations (Segment, Salesforce, HubSpot, Marketo)
  are configured with per-account API keys inside the Mutiny dashboard; Mutiny
  does not publish a general-purpose REST API.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/mutiny-hq-authentication"

All security posture

curl "https://apis.io/api/v1/security?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.