accueil / serveurs / Recherche & Web / ai.aviado/health
ai.aviado/health
serveur MCP (Model Context Protocol) · aviado 1.0.0
Aucun comportement malveillant détecté au test comportemental.
Est-ce que ai.aviado/health est sûr ?
Au dernier audit MCP Hub, le serveur MCP « ai.aviado/health » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 11 outils
- build_starter_stack≈ 515 tokens
Starter stack (default 3, max 5) of recommendable supplements for a goal (e.g. 'insomnia', 'LDL cholesterol'), best-replicated app-visible evidence first; never Rx or research; biomarker-proxy rows are hypotheses. Not offered for cancer or other serious disease (no_match). One item per ingredient family, checked for supplement interactions with each other and with `exclude`, which also takes medications by generic name (checked against FDA labels: major picks dropped, moderate flagged; unlisted medications are NOT checked, so ask, then use get_supplement_interactions with `drug`). Each item: why, grade, study dose (context), PMIDs, cited cautions (an avoid-level caution leads as cautions_summary and in data.important_cautions: state those first), same-mechanism and interaction flags. include_claim_link is opt-in (default false): true stores a small claim record and returns data.claim.claim_url for saving the stack in a free Aviado account.
Paramètres, retour & exemple (4)
Paramètresgoal· string · requis
Goal, condition or biomarker (e.g. 'insomnia', 'LDL cholesterol')exclude· array · optionnel
Supplements the user takes or avoids, and medications by generic name (e.g. 'sertraline'): supplements are never suggested; medications are checked against every pickmax_items· integer · optionnel
Stack size (default 3, max 5)include_claim_link· boolean · optionnel
Opt in (default false): create a claim link, which stores a small record for 30 days (only when enabled)
Exemple d'appel{"name": "build_starter_stack", "arguments": {"goal": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - check_interaction≈ 350 tokens
Point check of one pair, about 1-3 KB: a and b are each a supplement (name or canonical_id) or a medication (generic name; salt forms merged, brand names not matched). Supplement + supplement uses curated interactions (components and classes included); supplement + medication uses FDA drug-label rows only; two medications are not covered (no_match). Returns verdict {found, severity, direction, summary, recommendation, recorded_for, evidence_level, sources} and coverage (level none/sparse/moderate/broad). found:false is NOT a safety answer: absence of a record is not evidence of safety, so read coverage and say so. Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (2)
Paramètresa· string · requis
First supplement (name or canonical id) or medication (generic name)b· string · requis
Second supplement (name or canonical id) or medication (generic name)
Exemple d'appel{"name": "check_interaction", "arguments": {"a": "texte", "b": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_biomarkers_for_supplement≈ 376 tokens
Biomarkers a supplement moves in the Aviado app's evidence graph, one entry per biomarker (strongest edge), ordered by prior_weight (graph evidence weight 0-1, not a calibrated probability or effect size). Each entry has direction (up/down/bidirectional), goal/subgoal, has_verified_support / mixed_evidence, up to 3 PubMed IDs (pmids; URL template in coverage) with n_studies / rct_count, and dose (mean study dose {value, unit}: evidence context, not a dosing recommendation; see coverage.dose_note); null fields are omitted. Partial and non-exhaustive: a missing biomarker is not evidence of no effect. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Max results (default 25, max 100)supplement· string · requis
Supplement name (e.g., 'fish oil', 'curcumin', 'vitamin D3')
Exemple d'appel{"name": "get_biomarkers_for_supplement", "arguments": {"supplement": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_interventions_for_biomarker≈ 468 tokens
All mixed interventions in Aviado's evidence graph that move a biomarker, each labelled with intervention_type: supplement, food_substance, prescription_drug, research_compound, research_nootropic, medical_compound, form_dependent, not_recommendable or unknown (omitted on plain recommendable supplement rows; see coverage.row_defaults). Rows that are not supplements are context, never a recommendation, and carry no dose or pathway details. Rows carry up to 3 PubMed IDs (pmids; URL template in coverage); optional direction (up/down) filters. graph_status (proven/suspected) is an internal eligibility label, not clinical validation; pathway_tags are raw graph metadata, not validated mechanisms. Coverage is partial and non-exhaustive; absence is not evidence of no effect (see coverage). The biomarker may be a name, an abbreviation, an Aviado id or a LOINC code (e.g. '4548-4'). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Max results (default 25, max 100)biomarker· string · requis
Biomarker name, abbreviation, or LOINC codedirection· string · optionnel · up | down
Only rows whose strongest edge moves the biomarker this way ('down' lowers it, 'up' raises it); bidirectional rows match neither
Exemple d'appel{"name": "get_interventions_for_biomarker", "arguments": {"biomarker": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_supplement_info≈ 297 tokens
Overview of one supplement: description, typical uses, its top 5 biomarkers (with up to 3 PubMed citations each), goals, mechanism tags and cited safety contraindications. Contraindications include those recorded for what it contains (e.g. turmeric shows curcumin's), labelled with recorded_for; only cited rows are shown, so an empty list is not proof of safety. For all biomarkers use get_biomarkers_for_supplement; for drug interactions use get_supplement_interactions. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (1)
Paramètressupplement· string · requis
Supplement name
Exemple d'appel{"name": "get_supplement_info", "arguments": {"supplement": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_supplement_interactions≈ 734 tokens
Drug interactions come only from FDA drug labels: thorough for supplements labels name often (St. John's wort, grapefruit, magnesium, ginkgo) and sparse or missing for most others (e.g. fish oil, vitamin K, berberine, ashwagandha); read coverage.drug, and never treat an empty or short list as proof of safety. To check one medication pass drug (generic name; salt forms merged, so 'warfarin' matches 'warfarin sodium'; brand names are not matched). Also returns curated supplement-supplement interactions (synergies, antagonisms, absorption conflicts, timing), except on a drug check unless include_supplement_interactions is true. Interactions recorded for what the supplement contains are included and labelled: fish oil returns EPA, DHA and omega-3 interactions, turmeric returns curcumin's (interaction_sources, recorded_for). Drug entries are one per drug, most severe first, paged with drug_limit/drug_offset (drug_page.total, next_offset); label_artifact_suspected marks an entry whose drug name contains the supplement only as a salt (e.g. esomeprazole magnesium) and whose text does not mention it. Data-source failures return an error, never an empty list. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (6)
Paramètresdrug· string · optionnel
Only return drug interactions for this drug: its generic name (e.g. 'warfarin', 'sertraline'), matched exactly with salt forms merged ('warfarin' matches 'warfarin sodium'); brand names are not matched. Supplement-supplement interactions are then omitted unless include_supplement_interactions is truedrug_limit· integer · optionnel
Max drug interactions to return (default 20, max 200)supplement· string · requis
Supplement namedrug_offset· integer · optionnel
Drug interactions to skip, for paging (use drug_page.next_offset)include_drug_interactions· boolean · optionnel
Include FDA drug-supplement interactionsinclude_supplement_interactions· boolean · optionnel
Include supplement-supplement interactions (default: true without drug, false when drug is given)
Exemple d'appel{"name": "get_supplement_interactions", "arguments": {"supplement": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_supplements_for_biomarker≈ 524 tokens
Supplements in Aviado's evidence graph that move a biomarker (e.g. 'LDL cholesterol', 'HbA1c'). Lists only registry-classified supplements: entities Aviado's identity vocabulary types as supplement, class or combination and marks recommendable; prescription drugs, research compounds, foods and unknown ids are excluded (use get_interventions_for_biomarker for all of them). Each hit has direction (up/down/bidirectional), prior_weight (evidence confidence 0-1, not effect size), graph_status (proven/suspected: internal eligibility labels, not clinical verification), has_verified_support / mixed_evidence, and dose (mean study dose {value, unit}: evidence context, not a dosing recommendation; see coverage.dose_note). Rows carry up to 3 PubMed IDs (pmids; URL template in coverage) with n_studies / rct_count; optional direction (up/down) filters. Null fields and default typing (coverage.row_defaults) are omitted per row. Results are partial and non-exhaustive; pathway_tags are raw graph metadata, not validated mechanisms. The biomarker may be a name, an abbreviation, an Aviado id or a LOINC code (e.g. '4548-4'). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Max results (default 25, max 100)biomarker· string · requis
Biomarker name, abbreviation, or LOINC codedirection· string · optionnel · up | down
Only rows whose strongest edge moves the biomarker this way ('down' lowers it, 'up' raises it); bidirectional rows match neither
Exemple d'appel{"name": "get_supplements_for_biomarker", "arguments": {"biomarker": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_supplements_for_condition≈ 544 tokens
Supplements associated with a health condition or goal (e.g. 'insomnia', 'anxiety', 'joint pain'), strongest evidence first. evidence_basis direct rows come from studies of the condition; biomarker_proxy rows are inferred from the supplement's effect on the named proxy_biomarkers (each backed by an effect the Aviado app shows), are hypotheses, and are graded at most D. Only recommendable supplements are listed by default (rows carry intervention_type, entity_type, regulatory_status and recommendable only where they differ from coverage.row_defaults; null fields are omitted); include_non_supplements lists prescription drugs and research compounds too, labelled, as context only. dose is a typical study dose {value, unit}: evidence context, not a dosing recommendation (coverage.dose_note). Partial: absence is not evidence a supplement does not help. A weak or ambiguous condition name returns needs_confirmation with candidate conditions; confirm one and pass its id. Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (4)
Paramètreslimit· integer · optionnel
Max supplements to return, ranked by evidence (default: 25, max: 50)condition· string · requis
Health condition, symptom, or goal (e.g., 'insomnia', 'anxiety', 'brain fog', 'joint pain')min_grade· string · optionnel · A | B | C | D
Minimum evidence grade to include (default: D = all)include_non_supplements· boolean · optionnel
Also list prescription drugs, research compounds and other non-recommendable entities, labelled (default false)
Exemple d'appel{"name": "get_supplements_for_condition", "arguments": {"condition": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_top_brands≈ 382 tokens
Highest-quality brands for a supplement: one product per brand (its best), ranked by ProofMark, Aviado's product quality score (testing, ingredients, transparency, manufacturing, certifications). proofmark_100 is the 0-100 score (proofmark = proofmark_100/100) with a letter grade; proofmark_status is graded, below_coverage_floor (assessed but too little evidence to score; not a low score) or not_scored, and only graded products carry a score. Retired catalog products are excluded. match_basis says whether products matched the supplement identity or a text search (less precise; may include multi-ingredient products). price, retailer and product_url come from scraped listings and may be missing or stale. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Number of results (max 20)supplement· string · requis
Supplement name
Exemple d'appel{"name": "get_top_brands", "arguments": {"supplement": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_conditions≈ 228 tokens
Find the condition id for a health condition, symptom or goal. Answers when the name matches one condition clearly (data.conditions lists it first, with up to 4 related suggestions); a weak or ambiguous name (e.g. 'blood pressure': high vs low) returns needs_confirmation with the suggestions in candidates. Ask the user which one they mean and pass its id as condition to get_supplements_for_condition.
Paramètres, retour & exemple (1)
Paramètresquery· string · requis
Search query (e.g., 'sleep', 'anxiety', 'brain fog', 'joint pain')
Exemple d'appel{"name": "search_conditions", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_supplements≈ 340 tokens
Find the Aviado id for a supplement name, exactly (no fuzzy matching). Answers with matches[0] = the identity: vocabulary_exact, or user_intent for salt/form names ('magnesium citrate' -> magnesium, with a form note). A name Aviado does not hold may be answered with a naming-model suggestion (match_type naming_slm_suggestion, identity false); confirm it with the user before using its id. Family names ('lithium') and confirm-only names return needs_confirmation with the members or candidates in candidates. Each match carries entity_type, regulatory_status and recommendable. Use mode='supplement_retail' only for raw retail product titles. Pass the confirmed canonical_id to the other supplement tools.
Paramètres, retour & exemple (2)
Paramètresmode· string · optionnel · identity | supplement_retail
Explicit routing mode; retail titles require supplement_retailquery· string · requis
Supplement identity or raw retail product title
Exemple d'appel{"name": "search_supplements", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
Badge pour votre README
Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.
[](https://dokore.fr/serveur/ai.aviado--health)
<a href="https://dokore.fr/serveur/ai.aviado--health"><img src="https://dokore.fr/badge/ai.aviado--health.svg" alt="Vérifié par MCP Hub" height="20"></a>
Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».