Cardiosense

aid: cardiosense
name: Cardiosense
description: Cardiosense, Inc. is a Chicago-based medical technology company developing AI-powered, noninvasive cardiac hemodynamic
  monitoring for heart failure care. Its CardioTag device is a wearable chest biosensor that captures seismocardiographic
  (SCG), electrocardiographic (ECG) and photoplethysmographic (PPG) signals, and its PCWP Analysis Software is a standalone
  AI software-as-a-medical-device that estimates Pulmonary Capillary Wedge Pressure from those signals without right heart
  catheterization or an implantable sensor. Both are authorized by the FDA as Class II medical devices, and the company received
  an FDA De Novo classification. Cardiosense publishes no developer program, SDK or API specification; its only machine-readable
  surfaces are an authored llms.txt, an extended AI-context document, an explicit AI-crawler allowance in robots.txt, and
  an OAuth-protected Model Context Protocol server on its own host.
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  generated: '2026-09-02'
  method: derived
image: https://cardiosense.com/wp-content/themes/hello-elementor-child/assets/images/social_1200.png
url: https://raw.githubusercontent.com/api-evangelist/cardiosense/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-09'
modified: '2026-08-09'
tags:
- Company
- Health
- Digital Health
- Medical Devices
- Cardiology
- Heart Failure
- Remote Patient Monitoring
- Wearables
- Artificial Intelligence
- Machine-Learning
- MCP
tags_raw:
- Company
- Health
- Digital Health
- Medical Devices
- Cardiology
- Heart Failure
- Remote Patient Monitoring
- Wearables
- Artificial Intelligence
- Machine Learning
- Model Context Protocol
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Cardiosense MCP Server
  description: A live Model Context Protocol endpoint served from the Cardiosense corporate host. It is a WordPress MCP Adapter
    deployment over the website's content and abilities rather than a product API for the CardioTag device or the PCWP Analysis
    Software. Anonymous JSON-RPC is rejected with HTTP 401, so the tool list and per-tool input schemas are not public. OAuth
    discovery for it is published anonymously at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
  humanURL: https://cardiosense.com/
  baseURL: https://cardiosense.com/wp-json/mcp/mcp-oauth-server
  tags:
  - MCP
  - Agents
  tags_raw:
  - Model Context Protocol
  - Agents
  properties:
  - type: MCPServer
    url: mcp/cardiosense-mcp.yml
  - type: Authentication
    url: authentication/cardiosense-authentication.yml
common:
- type: DomainSecurity
  url: security/cardiosense-domain-security.yml
- type: Website
  url: https://cardiosense.com/
- type: About
  url: https://cardiosense.com/about-us/
- type: Blog
  url: https://cardiosense.com/companynews/
- type: BlogRSS
  url: https://cardiosense.com/feed/
- type: PrivacyPolicy
  url: https://cardiosense.com/privacy-policy/
- type: GitHubOrganization
  url: https://github.com/Cardiosense
- type: LinkedIn
  url: https://www.linkedin.com/company/cardiosense
- type: Twitter
  url: https://x.com/cardiosenseinc
- type: Publications
  url: https://cardiosense.com/publications/
- type: Regulatory
  url: https://cardiosense.com/regulatory/
- type: LLMsTxt
  url: llms/cardiosense-llms.txt
- type: WellKnown
  url: well-known/cardiosense-well-known.yml
- type: MCPServer
  url: mcp/cardiosense-mcp.yml
- type: Authentication
  url: authentication/cardiosense-authentication.yml
- type: OAuthScopes
  url: scopes/cardiosense-scopes.yml
- type: Conformance
  url: conformance/cardiosense-conformance.yml
- type: Compliance
  url: conformance/cardiosense-conformance.yml
- type: RobotsTxt
  url: agentic-access/cardiosense-robots.txt
x-enrichment:
  date: '2026-08-09'
  status: enriched
  artifacts_added: 10
  pass: local-v1
x-coverage:
  state: covered
  detail: 'Cardiosense runs no developer program and publishes no API contract, but the profile is not empty: contract discovery
    turned up a hand-authored llms.txt, an llms-full.txt, an explicit AI-crawler allowance in robots.txt, and a live OAuth-protected
    Model Context Protocol server at /wp-json/mcp/mcp-oauth-server whose RFC 8414 and RFC 9728 discovery documents are served
    anonymously. The MCP tool list is the one thing still out of reach — tools/list and the backing WordPress Abilities registry
    both answer HTTP 401, so per-tool input schemas would need an mcp-scoped token. No OpenAPI, Swagger, GraphQL SDL, AsyncAPI,
    Postman collection or A2A agent card exists on any Cardiosense host.'
  evidence:
  - url: https://cardiosense.com/llms.txt
    status: 200
  - url: https://cardiosense.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://cardiosense.com/wp-json/mcp/mcp-oauth-server
    status: 401
  - url: https://cardiosense.com/openapi.json
    status: 404
  - url: https://cardiosense.com/.well-known/agent-card.json
    status: 404
  checked: '2026-08-09'