Bidwell Health
REMOTE · BIDWELL-HEALTH-CONNECTOR.NETLIFY.APP
Public Bidwell Health service information, state availability, care limits, and visit guidance.
Available components
Last scanned (21 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
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.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 739 tokens (~61/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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 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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +38
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
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 4 Nov 2026 · Probed https://bidwell-health-connector.netlify.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bidwell-health-connector.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.app. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bidwell-health-connector.netlify.app/mcp | Verified | 200 | |
| http (plaintext) | http://bidwell-health-connector.netlify.app/mcp | HTTPS enforced | 301 | https://bidwell-health-connector.netlify.app/mcp |
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 →
check_service_availability Check public service availability ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service identifier from list_care_options. |
| state | string | yes | State or territory code for the location being considered; not an address. |
No output schema declared.
No examples provided.
explain_visit Explain the visit process and price ~33
Read the public visit fee, payment terms, clinician-review requirement and service limitations. Does not book a visit or recommend treatment.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_assistant_policy Read the no-form-filling policy ~40
Read the public connector limits and website handoff policy. Screening, attestations, payment and care decisions are patient and clinician responsibilities on the practice website.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_bridge_refill_rules Understand a bridge refill before starting ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_intimate_health_education Explore BV, yeast, UTI and prevention education ~88
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_location_guidance Understand care while at home or traveling ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
get_next_step Find a useful next step ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service identifier from list_care_options. |
| state | string | yes | State or territory code for the location being considered; not an address. |
No output schema declared.
No examples provided.
get_online_care_boundaries Read when online care is not appropriate ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | – |
No output schema declared.
No examples provided.
get_practice_facts Read practice facts, credentials and visit terms ~32
Return sourced practice facts and independently verifiable public clinician credentials. No ratings, endorsements or personalized clinical claims.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_service_details Explain a service, options and common questions ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service identifier from list_care_options. |
| state | string | yes | State or territory code for the location being considered; not an address. |
No output schema declared.
No examples provided.
get_service_page Find the official service information page ~69
Return the official informational page for an available service and state. No intake is submitted and no personal information is carried in the link.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service identifier from list_care_options. |
| state | string | yes | State or territory code for the location being considered; not an address. |
No output schema declared.
No examples provided.
list_care_options Browse Bidwell services and states ~28
Read Bidwell Health’s public catalogue, including paused services. No personal information is needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · bidwell-health-connector.netlify.app
claude mcp add --transport http verdansk69-bidwell-health 'https://bidwell-health-connector.netlify.app/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.