# CloudMedico Public MCP (remote · cloudmedico.com)

Read-only CloudMedico product information with verified source links.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cloudmedico.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-cloudmedico-public-mcp/public-mcp.md), [page](https://verifymcp.io/servers/com-cloudmedico-public-mcp/public-mcp)

## Channel facts

- Endpoint: `https://cloudmedico.com/public-mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 340 tokens (~56/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CloudMedico Public MCP server?

CloudMedico Public MCP is a hosted endpoint at https://cloudmedico.com/public-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-cloudmedico-public-mcp 'https://cloudmedico.com/public-mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cloudmedico-public-mcp": {
      "url": "https://cloudmedico.com/public-mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cloudmedico-public-mcp": {
      "type": "http",
      "url": "https://cloudmedico.com/public-mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cloudmedico-public-mcp]
url = "https://cloudmedico.com/public-mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cloudmedico-public-mcp": {
      "type": "remote",
      "url": "https://cloudmedico.com/public-mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cloudmedico-public-mcp --url 'https://cloudmedico.com/public-mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cloudmedico-public-mcp:
    url: "https://cloudmedico.com/public-mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cloudmedico-public-mcp": {
      "Transport": "http",
      "Url": "https://cloudmedico.com/public-mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cloudmedico-public-mcp -t streamable-http -u 'https://cloudmedico.com/public-mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cloudmedico-public-mcp": {
      "type": "http",
      "url": "https://cloudmedico.com/public-mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `get_product_overview` (~44 tokens)

Product overview

Returns a concise CloudMedico public-product overview and canonical public source URLs. It never returns account, tenant, clinical, patient, registration, billing, or chatbot data.

Output parameters:

- `intendedUsers` (array)
- `productName`
- `sources` (array)
- `summary` (string)

### `search_public_knowledge` (~63 tokens)

Search public CloudMedico knowledge

Searches a bounded allow-list of verified public CloudMedico pages and returns canonical source URLs. It never searches tenant, account, clinical, patient, registration, billing, or chatbot data.

Input parameters:

- `query` (string, required): The public CloudMedico topic to search for.

Output parameters:

- `query` (string)
- `sources` (array)

### `get_features` (~60 tokens)

Feature information

Returns the canonical public CloudMedico feature page. It does not access account, tenant, clinical, patient, registration, billing, or chatbot data.

Input parameters:

- `category` (string|null): Optional CloudMedico feature category to use as context for the canonical source.

Output parameters:

- `category` (string|null)
- `sources` (array)

### `get_pricing` (~70 tokens)

Pricing information

Returns the canonical public CloudMedico pricing page. Pricing remains subject to the published page and market-specific qualifiers; the tool does not access account, tenant, clinical, patient, registration, billing, or chatbot data.

Input parameters:

- `market` (string|null): Optional market or country context for the published pricing information.

Output parameters:

- `market` (string|null)
- `sources` (array)

### `get_faq` (~58 tokens)

Frequently asked questions

Returns the canonical public CloudMedico FAQ page. It does not access account, tenant, clinical, patient, registration, billing, or chatbot data.

Input parameters:

- `topic` (string|null): Optional FAQ topic to use as context for the canonical source.

Output parameters:

- `sources` (array)
- `topic` (string|null)

### `get_ai_assistant_connections_overview` (~45 tokens)

AI assistant connections overview

Returns the canonical public CloudMedico AI assistant connections page. It does not access account, tenant, clinical, patient, registration, billing, or chatbot data.

Output parameters:

- `sources` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cloudmedico-public-mcp/public-mcp#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 83
- 2026-10-27: 82
- 2026-10-26: 82
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 76
- 2026-10-12: 75
- 2026-10-11: 75
- 2026-10-10: 74
- 2026-10-08: 73

## Common questions

### What is the CloudMedico Public MCP server?

CloudMedico Public MCP is listed in the public MCP registry as com.cloudmedico/public-mcp. Read-only CloudMedico product information with verified source links. This page covers its hosted endpoint (https://cloudmedico.com/public-mcp).

### Is the CloudMedico Public MCP server safe to use?

CloudMedico Public MCP scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CloudMedico Public MCP server expose?

CloudMedico Public MCP exposes 6 tools: get_product_overview, search_public_knowledge, get_features, get_pricing, get_faq, get_ai_assistant_connections_overview. Their descriptions and schemas cost roughly 340 tokens of context every time the server is loaded.

### Does the CloudMedico Public MCP server require authentication?

No. We connected to CloudMedico Public MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CloudMedico Public MCP server still maintained?

CloudMedico Public MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the CloudMedico Public MCP server?

VerifyMCP ran 13 checks on CloudMedico Public MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://cloudmedico.com/public-mcp
- Website: https://cloudmedico.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-cloudmedico-public-mcp/public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cloudmedico-public-mcp/public-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-cloudmedico-public-mcp/public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-cloudmedico-public-mcp/public-mcp