# io.github.Iomed-commits/elthio-mcp (remote · elthio-production.up.railway.app)

Supplement safety for AI agents. 1,500+ rules, NIH+FDA data, quality grading A-D.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `elthio-production.up.railway.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/iomed-commits-elthio-mcp/elthio-production.md), [page](https://verifymcp.io/servers/iomed-commits-elthio-mcp/elthio-production)

## Channel facts

- Endpoint: `https://elthio-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 568 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http iomed-commits-elthio-mcp 'https://elthio-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "iomed-commits-elthio-mcp": {
      "url": "https://elthio-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "iomed-commits-elthio-mcp": {
      "type": "http",
      "url": "https://elthio-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.iomed-commits-elthio-mcp]
url = "https://elthio-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iomed-commits-elthio-mcp": {
      "type": "remote",
      "url": "https://elthio-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add iomed-commits-elthio-mcp --url 'https://elthio-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  iomed-commits-elthio-mcp:
    url: "https://elthio-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "iomed-commits-elthio-mcp": {
      "Transport": "http",
      "Url": "https://elthio-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add iomed-commits-elthio-mcp -t streamable-http -u 'https://elthio-production.up.railway.app/mcp'
```

### Other

```json
{
  "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.

## 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-19 (score 71, +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-09-17 (score 70, +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-09-14 (score 69, +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.

### 2026-09-12 (score 68, +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.

### 2026-09-10 (score 67, +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.

### 2026-09-08 (score 66, +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.

### 2026-09-06 (score 65, +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.

### 2026-09-04 (score 64, +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.

## MCP tools (5)

### `check_supplement_safety` (~152 tokens)

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.

Input parameters:

- `medications` (array): List of user's prescription medications. e.g. ['Warfarin', 'Levothyroxine']
- `supplement` (string, required): 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.

### `grade_supplement_quality` (~114 tokens)

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.

Input parameters:

- `other_ingredients` (string): Other ingredients text from the label for filler detection. Optional.
- `supplement` (string, required): Supplement name to grade. e.g. 'Magnesium Oxide' or 'NOW Foods Vitamin D3 5000IU'

### `get_supplement_timing` (~95 tokens)

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.

Input parameters:

- `medications` (array): User's medications — affects timing recommendations.
- `supplement` (string, required): Supplement name. e.g. 'Magnesium Glycinate'

### `check_full_stack` (~134 tokens)

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.

Input parameters:

- `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, required): All supplements and vitamins.
- `wake_time` (string): Wake time in HH:MM format. e.g. '07:00'

### `verify_nih_label` (~73 tokens)

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.

Input parameters:

- `supplement` (string, required): Supplement name to verify against NIH DSLD.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/iomed-commits-elthio-mcp/elthio-production#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 69
- 2026-09-13: 68
- 2026-09-12: 68
- 2026-09-11: 67
- 2026-09-10: 67
- 2026-09-09: 66
- 2026-09-08: 66
- 2026-09-07: 65
- 2026-09-06: 65
- 2026-09-05: 64
- 2026-09-04: 64
- 2026-09-03: 63
- 2026-09-02: 63
- 2026-09-01: 62
- 2026-08-31: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://elthio-production.up.railway.app/mcp
- Repository: https://github.com/Iomed-commits/elthio-mcp
- Changelog RSS feed: https://verifymcp.io/servers/iomed-commits-elthio-mcp/elthio-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/iomed-commits-elthio-mcp/elthio-production.json
- HTML version of this page: https://verifymcp.io/servers/iomed-commits-elthio-mcp/elthio-production