# ClinicMarketIQ Public Data (remote · clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev)

Read-only U.S. healthcare dataset metadata, schemas, immutable downloads, and checksums.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev`: 77/100 (this document), [markdown](https://verifymcp.io/servers/evgeniy-yudin-clinicmarketiq-public-data/clinicmarketiq-public-mcp.md), [page](https://verifymcp.io/servers/evgeniy-yudin-clinicmarketiq-public-data/clinicmarketiq-public-mcp)

## Channel facts

- Endpoint: `https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/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-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 346 tokens (~57/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**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 31% of tool parameters carry a description.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the ClinicMarketIQ Public Data MCP server?

ClinicMarketIQ Public Data is a hosted endpoint at https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/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 evgeniy-yudin-clinicmarketiq-public-data 'https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "type": "http",
      "url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.evgeniy-yudin-clinicmarketiq-public-data]
url = "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "type": "remote",
      "url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add evgeniy-yudin-clinicmarketiq-public-data --url 'https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  evgeniy-yudin-clinicmarketiq-public-data:
    url: "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "Transport": "http",
      "Url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add evgeniy-yudin-clinicmarketiq-public-data -t streamable-http -u 'https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "type": "http",
      "url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/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-09-23 (score 77, +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-09-21 (score 76, +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-09-19 (score 75, +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-09-16 (score 74, +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-09-14 (score 73, +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-09-12 (score 72, +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-09-10 (score 71, +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-09-08 (score 70, +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)

### `list_datasets` (~43 tokens)

List ClinicMarketIQ datasets

List public ClinicMarketIQ dataset families from the canonical catalog. Returns metadata summaries, not observation rows.

Input parameters:

- `limit` (integer)
- `offset` (integer)

### `search_datasets` (~44 tokens)

Search ClinicMarketIQ datasets

Search public dataset family IDs, names, slugs, and publishers in the canonical ClinicMarketIQ catalog.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `get_dataset_metadata` (~52 tokens)

Get dataset metadata

Fetch the canonical public machine index for one ClinicMarketIQ dataset family, including provenance-facing download metadata and immutable manifest pointer.

Input parameters:

- `dataset` (string, required): Dataset family ID such as D02, or its catalog slug.

### `get_schema` (~64 tokens)

Get dataset schema

Fetch schema JSON declared by a dataset's immutable public manifest. If schema_name is omitted, returns all declared schemas (currently capped at 10).

Input parameters:

- `dataset` (string, required): Dataset family ID such as D02, or its catalog slug.
- `schema_name` (string)

### `get_download_url` (~66 tokens)

Get immutable download URL

Return canonical direct download URLs and declared SHA-256 values for a public dataset. This tool never proxies the dataset bytes.

Input parameters:

- `dataset` (string, required): Dataset family ID such as D02, or its catalog slug.
- `format` (string)
- `group` (string)

### `verify_checksum` (~77 tokens)

Verify a declared checksum

Compare a caller-provided SHA-256 digest with the canonical digest declared in the public dataset machine index. This bounded check does not download or re-hash large artifact bytes.

Input parameters:

- `dataset` (string, required): Dataset family ID such as D02, or its catalog slug.
- `filename` (string, required)
- `sha256` (string, required)

## Diagnostics

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

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 66
- 2026-08-30: 66
- 2026-08-29: 65
- 2026-08-28: 65
- 2026-08-27: 64

## Common questions

### What is the ClinicMarketIQ Public Data MCP server?

ClinicMarketIQ Public Data is an MCP server listed in the public MCP registry as io.github.evgeniy-yudin/clinicmarketiq-public-data. Read-only U.S. healthcare dataset metadata, schemas, immutable downloads, and checksums. This page covers its hosted endpoint (https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp).

### Is the ClinicMarketIQ Public Data MCP server safe to use?

ClinicMarketIQ Public Data scores 77 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 ClinicMarketIQ Public Data MCP server expose?

ClinicMarketIQ Public Data exposes 6 tools: list_datasets, search_datasets, get_dataset_metadata, get_schema, get_download_url, verify_checksum. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.

### Does the ClinicMarketIQ Public Data MCP server require authentication?

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

### Is the ClinicMarketIQ Public Data MCP server still maintained?

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

## Links

- Remote endpoint: https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp
- Repository: https://github.com/evgeniy-yudin/clinicmarketiq-data
- Website: https://clinicmarketiq.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/evgeniy-yudin-clinicmarketiq-public-data/clinicmarketiq-public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/evgeniy-yudin-clinicmarketiq-public-data/clinicmarketiq-public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/evgeniy-yudin-clinicmarketiq-public-data/clinicmarketiq-public-mcp