Koskamo

Elthio MCP

Elthio provides a supplement safety verification layer for AI agents, checking drug-supplement interactions, quality grades, NIH label verification, and filler detection before purchase or recommendation.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Elthio MCP logo, by ElthioCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Elthio
MCP endpoint (Streamable HTTP)
https://elthio-production.up.railway.app/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

6 of 6 have a description · 0 of 6 declare behavior hints · 6 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify drug-supplement interactions before purchase
  • Check supplement quality grade A-D
  • Verify NIH Dietary Supplement Label Database entries
  • Get personalized daily timing schedules for supplements

Source and maintenance

Community listingRegistry 1.0.1
Maintenance checked

Protocol and capabilities

Server
elthio 1.0.0
MCP protocol negotiated in check
2024-11-05
Tools
6 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

6 advertised

check_supplement_safety
Advertised by the server during the last successful anonymous check.

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.

check_supplement_safety input schema
{
  "type": "object",
  "required": [
    "supplement"
  ],
  "properties": {
    "supplement": {
      "type": "string",
      "description": "The supplement to check. Include brand and form for best results. e.g. 'Magnesium Bisglycinate 400mg' or 'Fish Oil 1000mg'"
    },
    "medications": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of user's prescription medications. e.g. ['Warfarin', 'Levothyroxine']"
    },
    "supplements": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "User's existing supplements for interaction checking."
    }
  }
}
grade_supplement_quality
Advertised by the server during the last successful anonymous check.

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.

grade_supplement_quality input schema
{
  "type": "object",
  "required": [
    "supplement"
  ],
  "properties": {
    "supplement": {
      "type": "string",
      "description": "Supplement name to grade. e.g. 'Magnesium Oxide' or 'NOW Foods Vitamin D3 5000IU'"
    },
    "other_ingredients": {
      "type": "string",
      "description": "Other ingredients text from the label for filler detection. Optional."
    }
  }
}
get_supplement_timing
Advertised by the server during the last successful anonymous check.

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.

get_supplement_timing input schema
{
  "type": "object",
  "required": [
    "supplement"
  ],
  "properties": {
    "supplement": {
      "type": "string",
      "description": "Supplement name. e.g. 'Magnesium Glycinate'"
    },
    "medications": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "User's medications — affects timing recommendations."
    }
  }
}
check_full_stack
Advertised by the server during the last successful anonymous check.

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.

check_full_stack input schema
{
  "type": "object",
  "required": [
    "supplements"
  ],
  "properties": {
    "bedtime": {
      "type": "string",
      "description": "Bedtime HH:MM"
    },
    "wake_time": {
      "type": "string",
      "description": "Wake time in HH:MM format. e.g. '07:00'"
    },
    "dinner_time": {
      "type": "string",
      "description": "Dinner time HH:MM"
    },
    "medications": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "All prescription medications."
    },
    "supplements": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "All supplements and vitamins."
    },
    "breakfast_time": {
      "type": "string",
      "description": "Breakfast time HH:MM"
    }
  }
}
verify_supplement_recommendation
Advertised by the server during the last successful anonymous check.

Verify whether a supplement is safe to recommend to a user given their medications and current supplements. Runs the same interaction check as /med-check plus pathway analysis on the full stack including the new supplement. Returns safe_to_recommend, agent_summary, confidence, severity, timing_recommendation, citation, full_interactions, and pathway_analysis. Use whenever an AI agent is about to suggest a supplement and needs a go/no-go safety verdict.

verify_supplement_recommendation input schema
{
  "type": "object",
  "required": [
    "supplement"
  ],
  "properties": {
    "context": {
      "type": "string",
      "description": "Optional — why the user wants this supplement (stored for audit only)."
    },
    "supplement": {
      "type": "string",
      "description": "Supplement the agent wants to recommend. e.g. 'Omega-3 Fish Oil 1000mg'"
    },
    "medications": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "User's prescription medications."
    },
    "supplements_already_taking": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Supplements the user already takes (excluding the one being recommended)."
    }
  }
}
verify_nih_label
Advertised by the server during the last successful anonymous check.

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.

verify_nih_label input schema
{
  "type": "object",
  "required": [
    "supplement"
  ],
  "properties": {
    "supplement": {
      "type": "string",
      "description": "Supplement name to verify against NIH DSLD."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1242 ms
95th percentile latency
1242 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1242 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http elthio-mcp https://elthio-production.up.railway.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add elthio-mcp --url https://elthio-production.up.railway.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable elthio-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "elthio-mcp": {
      "url": "https://elthio-production.up.railway.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "elthio-mcp": {
      "type": "streamableHttp",
      "url": "https://elthio-production.up.railway.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start elthio-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "elthio-mcp": {
      "type": "http",
      "url": "https://elthio-production.up.railway.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http elthio-mcp https://elthio-production.up.railway.app/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://elthio-production.up.railway.app/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "elthio-mcp": {
      "serverUrl": "https://elthio-production.up.railway.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Elthio MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.