Affinity Solutions · Authentication Profile

Affinity Solutions Authentication

Authentication

Affinity Solutions declares 2 security scheme(s) across its OpenAPI definitions.

CompanyDataAnalyticsConsumer Purchase DataTransaction DataMarketingAdvertisingMeasurementsFinancial ServicesRetailMCP
Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

oauth2_mcp oauth2
wordpress_application_password http

Source

Authentication Profile

affinity-solutions-authentication.yml Raw ↑
generated: '2026-09-12'
method: probed
source: https://www.affinity.solutions/.well-known/oauth-authorization-server
note: >-
  Derived from the provider's own RFC 8414 authorization-server metadata document and the RFC 9728
  protected-resource document, both fetched anonymously at HTTP 200. derive-authentication.py produced
  nothing because the provider publishes no OpenAPI; these fields are read verbatim from the discovery
  documents, not inferred.
schemes:
- name: oauth2_mcp
  type: oauth2
  flow: authorization_code
  pkce:
    required_methods: [S256]
  issuer: https://www.affinity.solutions
  authorization_endpoint: https://www.affinity.solutions/oauth/authorize
  token_endpoint: https://www.affinity.solutions/oauth/token
  revocation_endpoint: https://www.affinity.solutions/oauth/revoke
  grant_types_supported: [authorization_code, refresh_token]
  response_types_supported: [code]
  token_endpoint_auth_methods_supported: [none]
  scopes_supported: [mcp]
  client_registration:
    dynamic_registration_endpoint: null
    client_id_metadata_document_supported: true
    note: >-
      No RFC 7591 dynamic client registration endpoint is advertised. Instead the server declares
      client_id_metadata_document_supported, so a client identifies itself with a URL-shaped client_id
      resolving to its own metadata document. Public clients only (token_endpoint_auth_methods_supported
      is ["none"]), which is the OAuth 2.1 public-client-with-PKCE profile MCP expects.
  applies_to:
  - https://www.affinity.solutions/wp-json/mcp/mcp-oauth-server
- name: wordpress_application_password
  type: http
  http_scheme: basic
  source: https://www.affinity.solutions/wp-json/
  note: >-
    The site's WordPress REST root advertises application-passwords authentication with an authorization
    endpoint at /wp-admin/authorize-application.php. This gates the wp-abilities/v1 namespace and the
    second MCP endpoint. It is site-administration auth, not a customer API credential.
  applies_to:
  - https://www.affinity.solutions/wp-json/mcp/mcp-adapter-default-server
  - https://www.affinity.solutions/wp-json/wp-abilities/v1/
product_api_auth:
  documented: false
  note: >-
    No authentication documentation exists for the Comet / Consumer Purchase Insights data products.
    Access is contracted through clean rooms, a Snowflake Native App and managed services, none of which
    publish a public credential model.

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/affinity-solutions-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.

A second provider on the same verified email joins the account you already have.