B.O.N.S.A.I. Health Intelligence API
REMOTE · WEB-PRODUCTION-AE61.UP.RAILWAY.APP
Lifestyle medicine health intelligence via x402 micropayments. 637+ peer-reviewed references.
Available components
Last scanned (23 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 650 tokens (~72/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 5% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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://web-production-ae61.up.railway.app
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of web-production-ae61.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://web-production-ae61.up.railway.app | Verified | 200 | |
| http (plaintext) | http://web-production-ae61.up.railway.app | HTTPS enforced | 301 | https://web-production-ae61.up.railway.app/ |
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_interactions ~49
Check a list of medications for food-drug interactions, nutrient depletions, and timing-critical dosing requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| foods_or_supplements | array | – | – |
| medications | array | yes | – |
No output schema declared.
No examples provided.
drug_safety ~28
Return the food-drug safety profile for a single medication.
| Name | Type | Req | Description |
|---|---|---|---|
| medication | string | yes | – |
No output schema declared.
No examples provided.
get_protocol ~68
Generate an evidence-based whole-food plant-based protocol for one of 47 chronic conditions. Returns therapeutic foods, daily meal structure, foods to minimize, monitoring markers, and clinical citations.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | – |
| duration_weeks | integer | – | – |
| user_context | object | – | – |
No output schema declared.
No examples provided.
glp_phase_guide ~49
Return the protocol overview for a specific GLP-1 therapy phase (starting, titrating, maintenance, tapering, post_drug).
| Name | Type | Req | Description |
|---|---|---|---|
| glp1_phase | string | yes | – |
No output schema declared.
No examples provided.
glp_protocol ~95
Generate a GLP-aware nutrition protocol composed on top of any active chronic condition. Returns protein floor (1.2-1.6 g/kg), fiber ramp schedule, GI tolerance interventions, resistance training prescription, hydration target, and phase-specific guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | – | – |
| glp1_medication | string | yes | – |
| glp1_phase | string | yes | – |
| user_context | object | – | – |
No output schema declared.
No examples provided.
interpret_labs ~127
Interpret a panel of lab values against ACLM-optimized reference ranges. Returns risk classification per marker, lifestyle interventions, and medication deprescription signals.
| Name | Type | Req | Description |
|---|---|---|---|
| current_medications | array | – | – |
| health_goals | array | – | – |
| lab_values | object | yes | Key-value pairs of biomarker names and values. Common keys: hba1c, fasting_glucose, fasting_insulin, ldl, hdl, triglycerides, apob, lp_a, hscrp, vitamin_d, b12, ferritin, tsh, free_t4, free_t3. |
No output schema declared.
No examples provided.
lifestyle_query ~87
Ask any lifestyle medicine question. Returns evidence-based answer with citations from a 200-chunk knowledge base spanning ACLM 6-pillars, B.O.N.S.A.I. nutrition, drug-food interactions, lab interpretation, GLP guidance, wearables, and CGM signal interpretation.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| pillar | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
marker_reference ~59
Look up the ACLM-optimized reference range and lifestyle intervention plan for a single biomarker (e.g., apob, lp_a, hscrp, hba1c, fasting_insulin, vitamin_d).
| Name | Type | Req | Description |
|---|---|---|---|
| marker | string | yes | – |
No output schema declared.
No examples provided.
query_nutrition_topic ~51
Ask a nutrition or food-as-medicine question. Returns evidence-based answer from the 200-chunk lifestyle medicine knowledge base.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the B.O.N.S.A.I. Health Intelligence API MCP server?
B.O.N.S.A.I. Health Intelligence API is a hosted endpoint at https://web-production-ae61.up.railway.app/, 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 · web-production-ae61.up.railway.app
claude mcp add --transport http rabyavalla-bonsai-health 'https://web-production-ae61.up.railway.app/'
What is the B.O.N.S.A.I. Health Intelligence API MCP server?
B.O.N.S.A.I. Health Intelligence API is an MCP server listed in the public MCP registry as io.github.rabyavalla/bonsai-health. Lifestyle medicine health intelligence via x402 micropayments. 637+ peer-reviewed references. This page covers its hosted endpoint (https://web-production-ae61.up.railway.app).
Is the B.O.N.S.A.I. Health Intelligence API MCP server safe to use?
B.O.N.S.A.I. Health Intelligence API scores 78 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 B.O.N.S.A.I. Health Intelligence API MCP server expose?
B.O.N.S.A.I. Health Intelligence API exposes 9 tools: get_protocol, query_nutrition_topic, interpret_labs, marker_reference, glp_protocol, and 4 more. Their descriptions and schemas cost roughly 613 tokens of context every time the server is loaded.
Does the B.O.N.S.A.I. Health Intelligence API MCP server require authentication?
No. We connected to B.O.N.S.A.I. Health Intelligence API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the B.O.N.S.A.I. Health Intelligence API MCP server still maintained?
B.O.N.S.A.I. Health Intelligence API is still listed as active 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.