# Bidwell Health (remote · bidwell-health-connector.netlify.app)

Public Bidwell Health service information, state availability, care limits, and visit guidance.

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

> **Deprecated**: this server is marked deprecated in the MCP registry. The registry records this reason: "Superseded by com.bidwellhealth/connector. Use `https://tools.bidwellhealth.com/mcp.` The legacy endpoint remains available for existing connections."

## Components

- remote · `bidwell-health-connector.netlify.app`: 84/100 (this document), [markdown](https://verifymcp.io/servers/verdansk69-bidwell-health/bidwell-health-connector.md), [page](https://verifymcp.io/servers/verdansk69-bidwell-health/bidwell-health-connector)

## Channel facts

- Endpoint: `https://bidwell-health-connector.netlify.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.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**: 80/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 739 tokens (~61/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Bidwell Health MCP server?

Bidwell Health is a hosted endpoint at https://bidwell-health-connector.netlify.app/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 verdansk69-bidwell-health 'https://bidwell-health-connector.netlify.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "verdansk69-bidwell-health": {
      "url": "https://bidwell-health-connector.netlify.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "verdansk69-bidwell-health": {
      "type": "http",
      "url": "https://bidwell-health-connector.netlify.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.verdansk69-bidwell-health]
url = "https://bidwell-health-connector.netlify.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "verdansk69-bidwell-health": {
      "type": "remote",
      "url": "https://bidwell-health-connector.netlify.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add verdansk69-bidwell-health --url 'https://bidwell-health-connector.netlify.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  verdansk69-bidwell-health:
    url: "https://bidwell-health-connector.netlify.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "verdansk69-bidwell-health": {
      "Transport": "http",
      "Url": "https://bidwell-health-connector.netlify.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add verdansk69-bidwell-health -t streamable-http -u 'https://bidwell-health-connector.netlify.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "verdansk69-bidwell-health": {
      "type": "http",
      "url": "https://bidwell-health-connector.netlify.app/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 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-11-02 (score 83, +1)

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

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

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

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

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

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

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

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

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

### 2026-10-23 (score 78, +1)

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

### 2026-10-21 (score 77, +38)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.30

## MCP tools (12)

### `list_care_options` (~28 tokens)

Browse Bidwell services and states

Read Bidwell Health’s public catalogue, including paused services. No personal information is needed.

### `check_service_availability` (~83 tokens)

Check public service availability

Check whether a listed Bidwell service is offered in a state. This checks service scope, not personal medical eligibility. Inputs are limited to service and state; symptoms and identifying information are not accepted.

Input parameters:

- `service` (string, required): Service identifier from list_care_options.
- `state` (string, required): State or territory code for the location being considered; not an address.

### `get_service_details` (~94 tokens)

Explain a service, options and common questions

Read the current official service guide: who it serves, published medication options, preparation, pharmacy arrangements, limits, expected timelines and FAQs when published. General education only; no symptoms or personal details accepted. Returns sourced service details, not an individual treatment recommendation.

Input parameters:

- `service` (string, required): Service identifier from list_care_options.
- `state` (string, required): State or territory code for the location being considered; not an address.

### `explain_visit` (~33 tokens)

Explain the visit process and price

Read the public visit fee, payment terms, clinician-review requirement and service limitations. Does not book a visit or recommend treatment.

### `get_service_page` (~69 tokens)

Find the official service information page

Return the official informational page for an available service and state. No intake is submitted and no personal information is carried in the link.

Input parameters:

- `service` (string, required): Service identifier from list_care_options.
- `state` (string, required): State or territory code for the location being considered; not an address.

### `get_online_care_boundaries` (~61 tokens)

Read when online care is not appropriate

Read sourced general boundaries and emergency guidance for a service. No symptom questions or personal screening; this does not determine individual eligibility or safety. Excerpts are checked against the current website and fail closed if they change.

Input parameters:

- `service` (string, required)

### `get_bridge_refill_rules` (~53 tokens)

Understand a bridge refill before starting

Read the published stable-dose, monitoring, supply, documentation and medication-exclusion rules. Medication names, prescriptions, photos and personal history are not accepted as inputs. This is not approval to refill a particular drug.

### `get_location_guidance` (~70 tokens)

Understand care while at home or traveling

Explain the physical-location rule, including visitors and short stays. State is where care would take place, not home residence. No address, travel dates, itinerary or personal information accepted. A layover does not guarantee completion before departure.

Input parameters:

- `situation` (string, required)
- `state` (string, required)

### `get_next_step` (~88 tokens)

Find a useful next step

Return a public guide, the Start Visit picker when available, a state waitlist for unsupported locations, or portal sign-in for existing patients. No direct intake or checkout links, no form filling, and no private portal access.

Input parameters:

- `service` (string, required): Service identifier from list_care_options.
- `state` (string, required): State or territory code for the location being considered; not an address.

### `get_practice_facts` (~32 tokens)

Read practice facts, credentials and visit terms

Return sourced practice facts and independently verifiable public clinician credentials. No ratings, endorsements or personalized clinical claims.

### `get_assistant_policy` (~40 tokens)

Read the no-form-filling policy

Read the public connector limits and website handoff policy. Screening, attestations, payment and care decisions are patient and clinician responsibilities on the practice website.

### `get_intimate_health_education` (~88 tokens)

Explore BV, yeast, UTI and prevention education

Read a general, unranked comparison of BV, vaginal yeast and UTI, with linked prevention and recurrence research on probiotics, D-mannose and other options, plus an interactive learning guide. Accepts no inputs: never send symptoms, quiz answers, selections or personal details. This is education and question preparation, not symptom assessment, diagnosis, treatment selection or individual eligibility.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/verdansk69-bidwell-health/bidwell-health-connector#diagnostics

## Score history

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

## Common questions

### What is the Bidwell Health MCP server?

Bidwell Health is an MCP server listed in the public MCP registry as io.github.verdansk69/bidwell-health. Public Bidwell Health service information, state availability, care limits, and visit guidance. This page covers its hosted endpoint (https://bidwell-health-connector.netlify.app/mcp).

### Is the Bidwell Health MCP server safe to use?

Bidwell Health scores 84 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 Bidwell Health MCP server expose?

Bidwell Health exposes 12 tools: list_care_options, check_service_availability, get_service_details, explain_visit, get_service_page, and 7 more. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.

### Does the Bidwell Health MCP server require authentication?

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

### Is the Bidwell Health MCP server still maintained?

Bidwell Health is marked deprecated 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.

## Links

- Remote endpoint: https://bidwell-health-connector.netlify.app/mcp
- Website: https://bidwell-health-connector.netlify.app/
- Changelog RSS feed: https://verifymcp.io/servers/verdansk69-bidwell-health/bidwell-health-connector.xml
- Changelog JSON feed: https://verifymcp.io/servers/verdansk69-bidwell-health/bidwell-health-connector.json
- HTML version of this page: https://verifymcp.io/servers/verdansk69-bidwell-health/bidwell-health-connector