Impulse Dynamics · Authentication Profile

Impulse Dynamics Authentication

Authentication

Impulse Dynamics secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyMedical DevicesHealthcareCardiologyHeart FailureImplantable DevicesHealth TechnologyLife SciencesClinical TrialsMCPWordPress
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: header

Security Schemes

wpApplicationPassword http
scheme: basic
wpNonce apiKey
· in: header (X-WP-Nonce)
mcpAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-08-23'
method: derived
source: openapi/impulse-dynamics-mcp-api-openapi.yml, openapi/impulse-dynamics-oembed-1-0-api-openapi.yml,
  openapi/impulse-dynamics-root-api-openapi.yml, openapi/impulse-dynamics-wp-abilities-v1-api-openapi.yml,
  openapi/impulse-dynamics-wp-v2-api-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: wpApplicationPassword
  type: http
  scheme: basic
  description: 'WordPress Application Passwords. The live discovery document advertises this
    as the site''s only machine authentication method: authentication.application-passwords.endpoints.authorization
    = https://impulse-dynamics.com/wp-admin/authorize-application.php (fetched 2026-08-23).'
  sources:
  - openapi/impulse-dynamics-mcp-api-openapi.yml
  - openapi/impulse-dynamics-oembed-1-0-api-openapi.yml
  - openapi/impulse-dynamics-root-api-openapi.yml
  - openapi/impulse-dynamics-wp-abilities-v1-api-openapi.yml
  - openapi/impulse-dynamics-wp-v2-api-openapi.yml
- name: wpNonce
  type: apiKey
  in: header
  parameter: X-WP-Nonce
  description: WordPress cookie-authentication nonce, used by same-origin browser clients.
  sources:
  - openapi/impulse-dynamics-mcp-api-openapi.yml
  - openapi/impulse-dynamics-oembed-1-0-api-openapi.yml
  - openapi/impulse-dynamics-root-api-openapi.yml
  - openapi/impulse-dynamics-wp-abilities-v1-api-openapi.yml
  - openapi/impulse-dynamics-wp-v2-api-openapi.yml
- name: mcpAuth
  type: http
  scheme: bearer
  description: Bearer authentication guarding the `mcp` namespace. Anonymous POST of a JSON-RPC
    tools/list to https://impulse-dynamics.com/wp-json/mcp/mcp-oauth-server returned HTTP 401
    `mcp_unauthorized` and to https://impulse-dynamics.com/wp-json/mcp/mcp-adapter-default-server
    returned HTTP 401 `rest_forbidden` on 2026-08-23. This host publishes NO RFC 8414 authorization-server
    metadata and NO RFC 9728 protect
  sources:
  - openapi/impulse-dynamics-mcp-api-openapi.yml
  - openapi/impulse-dynamics-oembed-1-0-api-openapi.yml
  - openapi/impulse-dynamics-root-api-openapi.yml
  - openapi/impulse-dynamics-wp-abilities-v1-api-openapi.yml
  - openapi/impulse-dynamics-wp-v2-api-openapi.yml

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/impulse-dynamics-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 email required.

GitHub Google LinkedIn

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