# Medicare Pricing (remote · gateway.pipeworx.io)

What does Medicare PAY — physician fee schedule, lab rates, and per-day unit

- Trust score: 42/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `gateway.pipeworx.io`: 42/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-medicare-pricing/medicare-pricing-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-medicare-pricing/medicare-pricing-mcp)

## Channel facts

- Endpoint: `https://gateway.pipeworx.io/medicare-pricing/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-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 177 tokens (~177/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params.
  - Nothing to assess: this server has no tools to check for usage examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 5 days we've observed: 43 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Medicare Pricing MCP server?

Medicare Pricing is a hosted endpoint at https://gateway.pipeworx.io/medicare-pricing/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 pipeworx-io-medicare-pricing 'https://gateway.pipeworx.io/medicare-pricing/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-medicare-pricing": {
      "url": "https://gateway.pipeworx.io/medicare-pricing/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-medicare-pricing": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/medicare-pricing/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pipeworx-io-medicare-pricing]
url = "https://gateway.pipeworx.io/medicare-pricing/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-medicare-pricing": {
      "type": "remote",
      "url": "https://gateway.pipeworx.io/medicare-pricing/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-medicare-pricing --url 'https://gateway.pipeworx.io/medicare-pricing/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-medicare-pricing:
    url: "https://gateway.pipeworx.io/medicare-pricing/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-medicare-pricing": {
      "Transport": "http",
      "Url": "https://gateway.pipeworx.io/medicare-pricing/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-medicare-pricing -t streamable-http -u 'https://gateway.pipeworx.io/medicare-pricing/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-medicare-pricing": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/medicare-pricing/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-20 (score 42, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 42, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-18 (score 42, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-17 (score 42, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-16 (score 42, −16)

- [security regression] Stability: unverified → fail
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Schema quality: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: 400 → 177
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-15 (score 58)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

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

## Score history

- 2026-09-20: 42
- 2026-09-19: 42
- 2026-09-18: 42
- 2026-09-17: 42
- 2026-09-16: 42
- 2026-09-15: 58

## Common questions

### What is the Medicare Pricing MCP server?

Medicare Pricing is an MCP server listed in the public MCP registry as io.github.pipeworx-io/medicare-pricing. What does Medicare PAY, physician fee schedule, lab rates, and per-day unit. This page covers its hosted endpoint (https://gateway.pipeworx.io/medicare-pricing/mcp).

### Is the Medicare Pricing MCP server safe to use?

Medicare Pricing scores 42 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.

### Does the Medicare Pricing MCP server require authentication?

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

### Is the Medicare Pricing MCP server still maintained?

Medicare Pricing is still listed as active in the MCP registry. We last reached this channel on 20 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://gateway.pipeworx.io/medicare-pricing/mcp
- Repository: https://github.com/pipeworx-io/mcp-medicare-pricing
- Website: https://pipeworx.io/packs/medicare-pricing
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-medicare-pricing/medicare-pricing-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-medicare-pricing/medicare-pricing-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-medicare-pricing/medicare-pricing-mcp