Local Infusion · Authentication Profile

Local Infusion Authentication

Authentication

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

CompanyHealthcareHealth ServicesInfusion TherapySpecialty PharmacyAmbulatory CarePatient ServicesAutoimmuneChronic CareMCPWordPress

Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in: header

Security Schemes

mcpOAuth2 oauth2

· flows: authorizationCode

wpNonce apiKey

· in: header (X-WP-Nonce)

Source

Authentication Profile

generated: '2026-08-25'
method: derived
source: openapi/local-infusion-mcp-api-openapi.yml, openapi/local-infusion-oembed-1-0-api-openapi.yml,
  openapi/local-infusion-root-api-openapi.yml, openapi/local-infusion-wp-abilities-v1-api-openapi.yml,
  openapi/local-infusion-wp-v2-api-openapi.yml
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
schemes:
- name: mcpOAuth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mylocalinfusion.com/oauth/authorize
    tokenUrl: https://mylocalinfusion.com/oauth/token
    scopes: 1
  description: OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC
    8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-server (fetched
    2026-08-25, HTTP 200). Guards the `mcp` namespace; the RFC 9728 protected-resource metadata
    names https://mylocalinfusion.com/wp-json/mcp/mcp-oauth-server.
  sources:
  - openapi/local-infusion-mcp-api-openapi.yml
  - openapi/local-infusion-oembed-1-0-api-openapi.yml
  - openapi/local-infusion-root-api-openapi.yml
  - openapi/local-infusion-wp-abilities-v1-api-openapi.yml
  - openapi/local-infusion-wp-v2-api-openapi.yml
- name: wpNonce
  type: apiKey
  in: header
  parameter: X-WP-Nonce
  description: WordPress cookie-authentication nonce. Advertised by the live server in its Access-Control-Allow-Headers
    response header (Authorization, X-WP-Nonce, Content-Disposition, Content-MD5, Content-Type),
    observed on a 401 from the MCP endpoint.
  sources:
  - openapi/local-infusion-mcp-api-openapi.yml
  - openapi/local-infusion-oembed-1-0-api-openapi.yml
  - openapi/local-infusion-root-api-openapi.yml
  - openapi/local-infusion-wp-abilities-v1-api-openapi.yml
  - openapi/local-infusion-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/local-infusion-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.