Cardiosense

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.

Cardiosense publishes 1 API on the APIs.io network. Tagged areas include Company, Health, Digital Health, Medical Devices, and Cardiology.

Cardiosense’s developer surface includes engineering blog, authentication, and 17 more developer resources.

🌐 Visit website 📡 Source on GitHub
23.2/100 emerging ▬ flat Agent 20/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs 1 MCP Servers
CompanyHealthDigital HealthMedical DevicesCardiologyHeart FailureRemote Patient MonitoringWearablesArtificial IntelligenceMachine LearningModel Context Protocol

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 23.2/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 3.7 / 17
Commercial Clarity 3.1 / 17
Operational Transparency 0.6 / 11
Governance 1.3 / 10
Discoverability 6.5 / 9
Regulatory Posture 8.1 / 15
Agent readiness — 20/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/cardiosense: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Cardiosense MCP Server

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 ...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

cardiosense-mcp.yml

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Cardiosense Authentication

2 schemes

SECURITY

Cardiosense Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Cardiosense Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 WellKnown
WellKnown
 MCPServer
MCPServer

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication
 OAuthScopes
OAuthScopes
 Compliance
Compliance

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy
PrivacyPolicy

Company 6

The organization behind the API

Website
Website
 About
About
 Blog
Blog
 BlogRSS
BlogRSS
 LinkedIn
LinkedIn
 Twitter
Twitter

Other 3

Properties that don't map to a standard resource type

Publications
Publications
 Regulatory
Regulatory
 RobotsTxt
RobotsTxt

Source (apis.yml)

apis.yml Raw ↑ 
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.
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.20'
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
- 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:
  - 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'