# Cardiosense MCP Server

**Canonical:** https://apis.io/apis/cardiosense/cardiosense-mcp-server/  
**Provider:** Cardiosense — https://apis.io/providers/cardiosense/  
**Base URL:** https://cardiosense.com/wp-json/mcp/mcp-oauth-server  
**Documentation:** https://cardiosense.com/

Cardiosense MCP Server is published by [Cardiosense](https://apis.io/providers/cardiosense/) on the [APIs.io](https://apis.io/) network. Tagged areas include MCP and Agents. The published artifact set on APIs.io includes authentication docs.

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.

## Machine-readable artifacts (3)

- **MCPServer** — https://raw.githubusercontent.com/api-evangelist/cardiosense/refs/heads/main/mcp/cardiosense-mcp.yml
- **Authentication** — https://raw.githubusercontent.com/api-evangelist/cardiosense/refs/heads/main/authentication/cardiosense-authentication.yml
- **APIsJSON** — https://raw.githubusercontent.com/api-evangelist/cardiosense/refs/heads/main/apis.yml

## Tags

MCP, Agents

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/cardiosense/cardiosense-mcp-server/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/cardiosense/.