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.

ClinicMarketIQ Public Data

REMOTE · CLINICMARKETIQ-PUBLIC-MCP.ROTGAR-FIZKL.WORKERS.DEV · SCANNED SEP 24

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

+3 this week 77 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 346 tokens (~57/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 Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 31% of tool parameters carry a description.Partial
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 current MCP spec version (2026-07-28).Pass
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.

remote · clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev

# add to Claude Code
claude mcp add --transport http evgeniy-yudin-clinicmarketiq-public-data 'https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "type": "http",
      "url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add evgeniy-yudin-clinicmarketiq-public-data --url 'https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  evgeniy-yudin-clinicmarketiq-public-data:
    url: "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "evgeniy-yudin-clinicmarketiq-public-data": {
      "Transport": "http",
      "Url": "https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add evgeniy-yudin-clinicmarketiq-public-data -t streamable-http -u 'https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp'
// mcp.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 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.

  • 23 Sept 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.

  • 21 Sept 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.

  • 19 Sept 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.

  • 16 Sept 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.

  • 14 Sept 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.

  • 12 Sept 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.

  • 10 Sept 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.

  • 8 Sept 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 24 Sept 2026 · Probed https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rotgar-fizkl.workers.dev CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 4cb525cf1364c90d139100f897182058
SANs: rotgar-fizkl.workers.dev, *.rotgar-fizkl.workers.dev
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 insecure

Validation of clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp Verified 200
http (plaintext) http://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp Inconclusive 405
MCP tools · 6 exposed · ~346 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_dataset_metadata ~52

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

NameTypeReqDescription
datasetstringyesDataset family ID such as D02, or its catalog slug.

No output schema declared.

No examples provided.

get_download_url ~66

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

NameTypeReqDescription
datasetstringyesDataset family ID such as D02, or its catalog slug.
formatstring––
groupstring––

No output schema declared.

No examples provided.

get_schema ~64

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

NameTypeReqDescription
datasetstringyesDataset family ID such as D02, or its catalog slug.
schema_namestring––

No output schema declared.

No examples provided.

list_datasets ~43

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

NameTypeReqDescription
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

search_datasets ~44

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

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

verify_checksum ~77

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.

NameTypeReqDescription
datasetstringyesDataset family ID such as D02, or its catalog slug.
filenamestringyes–
sha256stringyes–

No output schema declared.

No examples provided.

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.