io.github.Iomed-commits/elthio-mcp
REMOTE · ELTHIO-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 20
Supplement safety for AI agents. 1,500+ rules, NIH+FDA data, quality grading A-D.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 568 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Iomed-commits/elthio-mcp server?
io.github.Iomed-commits/elthio-mcp is a hosted endpoint at https://elthio-production.up.railway.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 · elthio-production.up.railway.app
claude mcp add --transport http iomed-commits-elthio-mcp 'https://elthio-production.up.railway.app/mcp'
{
"mcpServers": {
"iomed-commits-elthio-mcp": {
"url": "https://elthio-production.up.railway.app/mcp"
}
}
} {
"servers": {
"iomed-commits-elthio-mcp": {
"type": "http",
"url": "https://elthio-production.up.railway.app/mcp"
}
}
} [mcp_servers.iomed-commits-elthio-mcp] url = "https://elthio-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"iomed-commits-elthio-mcp": {
"type": "remote",
"url": "https://elthio-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add iomed-commits-elthio-mcp --url 'https://elthio-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
iomed-commits-elthio-mcp:
url: "https://elthio-production.up.railway.app/mcp" {
"McpServers": {
"iomed-commits-elthio-mcp": {
"Transport": "http",
"Url": "https://elthio-production.up.railway.app/mcp"
}
}
} assistant mcp add iomed-commits-elthio-mcp -t streamable-http -u 'https://elthio-production.up.railway.app/mcp'
{
"mcpServers": {
"iomed-commits-elthio-mcp": {
"type": "http",
"url": "https://elthio-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 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.
- 17 Sept 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.
- 14 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.
- 12 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://elthio-production.up.railway.app/mcp
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=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 elthio-production.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://elthio-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://elthio-production.up.railway.app/mcp | HTTPS enforced | 301 | https://elthio-production.up.railway.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_full_stack ~134
Check a complete supplement and medication stack for all interactions, conflicts, synergies, and generate a full daily timing schedule. Use this when a user wants to check their entire supplement regimen or build a complete daily schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| bedtime | string | – | Bedtime HH:MM |
| breakfast_time | string | – | Breakfast time HH:MM |
| dinner_time | string | – | Dinner time HH:MM |
| medications | array | – | All prescription medications. |
| supplements | array | yes | All supplements and vitamins. |
| wake_time | string | – | Wake time in HH:MM format. e.g. '07:00' |
No output schema declared.
No examples provided.
check_supplement_safety ~152
Check if a supplement is safe with a user's medications and existing supplements. Returns interaction data, safety score, quality grade, filler detection, NIH verification, and timing recommendation. Use this whenever a user asks about supplement safety, drug interactions, or whether they can take a supplement with their medications.
| Name | Type | Req | Description |
|---|---|---|---|
| medications | array | – | List of user's prescription medications. e.g. ['Warfarin', 'Levothyroxine'] |
| supplement | string | yes | The supplement to check. Include brand and form for best results. e.g. 'Magnesium Bisglycinate 400mg' or 'Fish Oil 1000mg' |
| supplements | array | – | User's existing supplements for interaction checking. |
No output schema declared.
No examples provided.
get_supplement_timing ~95
Get the optimal time to take a supplement and why. Returns slot (morning/bedtime/with food/etc), clinical reasoning, and personalized instruction. Use this when a user asks when to take a supplement or how to build a timing schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| medications | array | – | User's medications — affects timing recommendations. |
| supplement | string | yes | Supplement name. e.g. 'Magnesium Glycinate' |
No output schema declared.
No examples provided.
grade_supplement_quality ~114
Get the quality grade (A-D) for a supplement based on bioavailability, filler detection, and NIH verification. Use this when a user asks about supplement quality, which form is best, whether a supplement has concerning fillers, or wants to compare brands.
| Name | Type | Req | Description |
|---|---|---|---|
| other_ingredients | string | – | Other ingredients text from the label for filler detection. Optional. |
| supplement | string | yes | Supplement name to grade. e.g. 'Magnesium Oxide' or 'NOW Foods Vitamin D3 5000IU' |
No output schema declared.
No examples provided.
verify_nih_label ~73
Verify if a supplement matches a record in the NIH Dietary Supplement Label Database (DSLD). Returns verification status, DSLD ID, and confidence level. Use this when a user asks if a supplement is legitimate or wants to verify label accuracy.
| Name | Type | Req | Description |
|---|---|---|---|
| supplement | string | yes | Supplement name to verify against NIH DSLD. |
No output schema declared.
No examples provided.
What is the io.github.Iomed-commits/elthio-mcp server?
io.github.Iomed-commits/elthio-mcp is listed in the public MCP registry as io.github.Iomed-commits/elthio-mcp. Supplement safety for AI agents. 1,500+ rules, NIH+FDA data, quality grading A-D. This page covers its hosted endpoint (https://elthio-production.up.railway.app/mcp).
Is the io.github.Iomed-commits/elthio-mcp server safe to use?
io.github.Iomed-commits/elthio-mcp scores 71 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 io.github.Iomed-commits/elthio-mcp server expose?
io.github.Iomed-commits/elthio-mcp exposes 5 tools: check_supplement_safety, grade_supplement_quality, get_supplement_timing, check_full_stack, verify_nih_label. Their descriptions and schemas cost roughly 568 tokens of context every time the server is loaded.
Does the io.github.Iomed-commits/elthio-mcp server require authentication?
No. We connected to io.github.Iomed-commits/elthio-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Iomed-commits/elthio-mcp server still maintained?
io.github.Iomed-commits/elthio-mcp 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.