Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CloudMedico Public MCP

REMOTE · CLOUDMEDICO.COM

Read-only CloudMedico product information with verified source links.

Available components

+3 this week 86 Trust /100

Last scanned (13 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security77
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 340 tokens (~56/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +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.

  • 2 Nov 26 +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.

  • 31 Oct 26 +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.

  • 28 Oct 26 +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.

  • 26 Oct 26 +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.

  • 24 Oct 26 +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.

  • 22 Oct 26 +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.

  • 20 Oct 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://cloudmedico.com/public-mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cloudmedico.com CN=WE1,O=Google Trust Services,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA256 e10899871621f04b1329d0d536ca5481
SANs: cloudmedico.com, *.cloudmedico.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of cloudmedico.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cloudmedico.com. present 2371 13 Verified
cloudmedico.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cloudmedico.com/public-mcp Verified 200
http (plaintext) http://cloudmedico.com/public-mcp HTTPS enforced 301 https://cloudmedico.com/public-mcp
MCP tools · 6 exposed · ~340 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_ai_assistant_connections_overview ~45

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
sourcesarrayyes–

No examples provided.

get_faq ~58

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

NameTypeReqDescription
topicstring|null–Optional FAQ topic to use as context for the canonical source.
NameTypeReqDescription
sourcesarrayyes–
topicstring|nullyes–

No examples provided.

get_features ~60

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

NameTypeReqDescription
categorystring|null–Optional CloudMedico feature category to use as context for the canonical source.
NameTypeReqDescription
categorystring|nullyes–
sourcesarrayyes–

No examples provided.

get_pricing ~70

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.

NameTypeReqDescription
marketstring|null–Optional market or country context for the published pricing information.
NameTypeReqDescription
marketstring|nullyes–
sourcesarrayyes–

No examples provided.

get_product_overview ~44

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
intendedUsersarrayyes–
productName–yes–
sourcesarrayyes–
summarystringyes–

No examples provided.

search_public_knowledge ~63

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.

NameTypeReqDescription
querystringyesThe public CloudMedico topic to search for.
NameTypeReqDescription
querystringyes–
sourcesarrayyes–

No examples provided.

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.

remote · cloudmedico.com

# add to Claude Code
claude mcp add --transport http com-cloudmedico-public-mcp 'https://cloudmedico.com/public-mcp'
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.