Cardiosense

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

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/cardiosense/refs/heads/main/authentication/cardiosense-authentication.yml

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/cardiosense/refs/heads/main/mcp/cardiosense-mcp.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/cardiosense/refs/heads/main/apis.yml

API entry from apis.yml

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