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 is listed with 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 📡 Profile data on GitHub

18.0/100 emerging ▬ flat Agent 17/100 agent aware Front door AI 3/6 light Heartbeat 48/100 slowing Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers

Company Health Digital Health Medical Devices Cardiology Heart Failure Remote Patient Monitoring Wearables Artificial Intelligence Machine Learning MCP

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 18.0/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.2 / 17

Access Clarity 2.2 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 4.5 / 15

Agent readiness — 17/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/cardiosense/"><img src="https://apis.io/badge/cardiosense/card.svg" alt="Cardiosense on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 13.1 — up to +17.4 composite points
Access Clarity scores 13.2 — up to +17.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/cardiosense/apis.yml: open an issue on github.com/api-evangelist/cardiosense to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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
FDA Device Establishments (radiology, nuclear medicine, cardiovascular, robotic surgery)	regulated	40.7 (thin)	-	-

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 2

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.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

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 Server

Cardiosense serves a live Model Context Protocol server from its own primary host. It is not a product API: Cardiosense sells an FDA-cleared Class II cardiac monitoring device, ...

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

1 scope

1 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

Authentication

OAuthScopes

Compliance

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 6

The organization behind the API

Website

About

Blog

BlogRSS

LinkedIn

Twitter

Twitter

Other 3

Properties that don't map to a standard resource type

Publications

Publications

Regulatory

Regulatory

RobotsTxt

RobotsTxt

Source (apis.yml)

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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: covered
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  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
- Machine-Learning
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
  x-surface: platform-generated
  x-platform: wordpress
  x-platform-surface: mcp-plugin
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'

Cardiosense API — frequently asked questions

Does Cardiosense have an API?

Yes. APIs.io lists 1 API from Cardiosense, including Cardiosense MCP Server.

How do I authenticate with the Cardiosense API?

Cardiosense documents its authentication (2 schemes). The details are profiled on APIs.io as Cardiosense Authentication.

Does Cardiosense have an MCP server?

Yes. APIs.io lists 1 MCP server for Cardiosense: Cardiosense serves a live Model Context Protocol server from its own primary host. It is not a product API: Cardiosense sells an FDA-cleared Class II cardiac monitoring device, not a developer platfor

Is the Cardiosense API ready for AI agents?

Cardiosense has a Kin Score of 18.0 out of 100 (emerging) and an Agent Readiness score of 16.5 (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.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/cardiosense"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/cardiosense/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/cardiosense/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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