Axena Health
Axena Health, Inc. is a Waltham, Massachusetts women's health medical device company whose flagship product is the Leva Pelvic Health System, an FDA-cleared prescription digital therapeutic that pairs a vaginal motion sensor with a mobile app to deliver supervised pelvic floor muscle training for stress, mixed and mild-to-moderate urgency urinary incontinence and chronic fecal incontinence. Leva is prescribed by clinicians, dispensed to patients through telehealth and specialty channels, and is reimbursed through commercial health plans and federal channels including the Veterans Health Administration. Axena Health ships software only as a regulated end-user product: as of this profile it operates no developer portal, no public API reference, no SDKs and no partner integration program. The only machine-readable surfaces reachable without credentials are the default WordPress REST API on its two marketing sites and an OAuth-protected WordPress MCP Adapter endpoint on levacares.com.
Axena Health is profiled on the APIs.io network. Tagged areas include Company, Health, Digital Health, Medical Devices, and Women’s Health.
Axena Health’s developer surface includes engineering blog, support, authentication, and 14 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Digital Therapeutics (regulated, reimbursed digital health apps) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Leva Pelvic Health System — WordPress MCP Adapter
levacares.com — the Leva Pelvic Health System product site operated by Axena Health — runs the WordPress MCP Adapter and exposes two live Model Context Protocol endpoints under ...
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Source (apis.yml)
Axena Health API — frequently asked questions
How do I authenticate with the Axena Health API?
Axena Health uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Axena Health Authentication.
Does Axena Health have an MCP server?
Yes. APIs.io lists 1 MCP server for Axena Health: levacares.com — the Leva Pelvic Health System product site operated by Axena Health — runs the WordPress MCP Adapter and exposes two live Model Context Protocol endpoints under the `mcp` REST namespac
Is the Axena Health API ready for AI agents?
Axena Health has a Kin Score of 18.8 out of 100 (emerging) and an Agent Readiness score of 6.0 (agent-aware), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.