MCP server · Cardiosense

cardiosense-mcp.yml

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 platform, and this MCP surface is a WordPress MCP Adapter deployment sitting over the corporate website's content and abilities. It is nonetheless a real, deliberately configured agent surface — the company registered an OAuth authorization server, an RFC 9728 protected-resource document, and a dedicated `mcp` scope for it. Both servers reject anonymous JSON-RPC, so the tool list and per-tool inputSchemas could not be enumerated without credentials.

Open docs → Cardiosense provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Cardiosense Type: Documentation link Transport: Host: cardiosense.com

Documentation

https://cardiosense.com/wp-json/mcp

Documentation link · transport

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.