SuperMe · Authentication Profile

Superme Authentication

Authentication

SuperMe 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).

CompanyArtificial IntelligenceAI AgentsProfessional NetworkExpert KnowledgeModel Context ProtocolMCP
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

OAuth2 oauth2

Source

Authentication Profile

superme-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://mcp.superme.ai/.well-known/oauth-authorization-server
docs: https://superme.ai/mcp
summary:
  types: [oauth2]
  oauth2_flows: [authorizationCode]
  grant_types: [authorization_code, refresh_token]
  pkce: S256
  dynamic_client_registration: true    # RFC 7591 registration_endpoint present
  bearer_methods: [header]
schemes:
- name: OAuth2
  type: oauth2
  issuer: https://mcp.superme.ai/
  authorization_endpoint: https://mcp.superme.ai/authorize
  token_endpoint: https://mcp.superme.ai/token
  registration_endpoint: https://mcp.superme.ai/register
  token_endpoint_auth_methods_supported: [client_secret_post, client_secret_basic]
  code_challenge_methods_supported: [S256]
  response_types_supported: [code]
  sources:
  - well-known/superme-oauth-authorization-server.json
notes: >-
  Auth model derived from SuperMe's live OAuth 2.1 authorization-server metadata,
  which fronts the hosted MCP server (mcp.superme.ai). No public OpenAPI is
  published for the underlying REST API (api.superme.ai auto-docs disabled), so
  API-key/other scheme details are not documented publicly.