Natoma · Authentication Profile

Natoma Authentication

Authentication

Natoma secures its APIs with oauth2, apiKey, saml2, and scim across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyCybersecurityMCPAI AgentsIdentityAccess ManagementGovernanceSecurity
Methods: oauth2, apiKey, saml2, scim Schemes: 4 OAuth flows: authorizationCode API key in: env

Security Schemes

PlatformOAuth2 oauth2
ApiKey apiKey
· in: env ()
SAML2 SSO saml2
SCIM scim

Source

Authentication Profile

natoma-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://api.natoma.app/.well-known/oauth-authorization-server
docs: https://docs.natoma.ai/docs/enterprise/secure-access-to-natoma
summary:
  types: [oauth2, apiKey, saml2, scim]
  api_key_in: [env]
  oauth2_flows: [authorizationCode]
schemes:
- name: PlatformOAuth2
  type: oauth2
  flow: authorizationCode
  issuer: https://api.natoma.app/oauth
  authorization_url: https://api.natoma.app/oauth/authorize
  token_url: https://api.natoma.app/oauth/token
  registration_url: https://api.natoma.app/oauth/register
  revocation_url: https://api.natoma.app/oauth/revoke
  introspection_url: https://api.natoma.app/oauth/introspect
  pkce: [S256, plain]
  dynamic_client_registration: true
  token_endpoint_auth_methods: [none]
  note: >-
    OAuth 2.1-style authorization server the Natoma MCP platform advertises via
    RFC 8414 metadata; public clients (token_endpoint_auth_method none) with PKCE and
    RFC 7591 Dynamic Client Registration. Used by remote MCP clients.
- name: ApiKey
  type: apiKey
  in: env
  name_field: NATOMA_MCP_API_KEY
  note: API key used by the stdio gateway (@natomalabs/natoma-mcp-gateway) to authenticate to the platform.
- name: SAML2 SSO
  type: saml2
  note: >-
    SAML 2.0 SSO for the Natoma console via Microsoft Entra ID and the Okta
    Integration Network (OIN). Docs: entra-sso, okta-sso.
- name: SCIM
  type: scim
  note: >-
    SCIM 2.0 user/role provisioning from Microsoft Entra ID and Okta (group- and
    attribute-based role mapping to Natoma roles).
per_connector_auth: >-
  Each catalog connector authenticates to its downstream app independently (OAuth,
  scoped API key, service-account key, or PAT), managed centrally by Natoma.

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