Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

supplemental.pl — EU/PL food law

REMOTE · MCP.SUPPLEMENTAL.PL

EU/PL food law for supplement firms: health claims, novel food, GIS, C.L.A.I.M.S. Not legal advice.

+5 this week 80 Trust /100

Last scanned (18 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 Security66
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1365 tokens (~170/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management80
  • Stability observed for 24 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +3
    • Tool “check_health_claim” rewrote its description, which is the text the model reads security
    • Tool “get_article” rewrote its description, which is the text the model reads security
    • Tool “get_claim_foodlaw” rewrote its description, which is the text the model reads security
    • Tool “gis_notification_steps” rewrote its description, which is the text the model reads security
    • Tool “novel_food_status” rewrote its description, which is the text the model reads security
    • Tool “nutrition_calc” rewrote its description, which is the text the model reads security
    • Tool “search_articles” rewrote its description, which is the text the model reads security
    • Tool “search_claims_foodlaw” rewrote its description, which is the text the model reads security
    • Schema quality: 145 → 170 ▼ functional
    • Schema quality: fail → pass ▲ functional
    • Schema quality: good → excellent functional
    • “get_article” reworded the description of “url” cosmetic
    • “get_claim_foodlaw” reworded the description of “id” cosmetic
    • “search_claims_foodlaw” reworded the description of “substance” cosmetic
  • 16 Nov 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.

  • 14 Nov 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.

  • 11 Nov 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.

  • 9 Nov 26 +2
    • Tool coverage: 75% → 100% ▲ functional
    • “check_health_claim” reworded the description of “limit” cosmetic
    • “get_claim_foodlaw” reworded the description of “id” cosmetic
    • “get_claim_foodlaw” reworded the description of “lang” cosmetic
    • “novel_food_status” reworded the description of “limit” cosmetic
    • “nutrition_calc” reworded the description of “product_name” cosmetic
    • “search_claims_foodlaw” reworded the description of “lang” cosmetic
  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.supplemental.pl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=supplemental.pl CN=WE1,O=Google Trust Services,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 b05a46d4a9918fcd135ded17724cfc9d
SANs: supplemental.pl, mcp.supplemental.pl, *.mcp.supplemental.pl
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.supplemental.pl. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
pl. DS published 2782 8 Verified
supplemental.pl. DS published 2371 13 Verified
mcp.supplemental.pl. Verified address RRset verified with the apex keys
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://mcp.supplemental.pl/mcp Verified 200
http (plaintext) http://mcp.supplemental.pl/mcp Inconclusive 405
MCP tools · 8 exposed · ~1,223 tokens

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 →

Tool Tokens
check_health_claim ~165

Look up a nutrient/substance in the official EU Register of nutrition and health claims (European Commission data, refreshed weekly). Shows whether each claim is Authorised, Non-authorised or Revoked, its conditions of use, the EFSA question and the legal act. Example: substance "vitamin C", claim_text "immune system".

NameTypeReqDescription
claim_textstring–Optional words of the claim/function, e.g. "immune system".
langstring–Response language. Default: en.
limitinteger–Max results (default 10, max 25).
statusstring–Default: all.
substancestringyesNutrient or substance (English or Latin), e.g. "vitamin C", "glucomannan".

No output schema declared.

{"claim_text":"immune system","lang":"en","substance":"vitamin C"}
get_article ~132

Return one supplemental.pl knowledge article by URL or slug: summary, headings, a text excerpt, legal references named in it and its PL/EN/DE versions. Pass lang to get another language version. Example: url "novel-food-food-supplements-eu" (slug) or the full URL https://supplemental.pl/en/knowledge/novel-food-food-supplements-eu/.

NameTypeReqDescription
langstring–Response language. Default: en.
urlstringyesArticle URL on supplemental.pl or its slug, e.g. "novel-food-food-supplements-eu".

No output schema declared.

{"lang":"en","url":"novel-food-food-supplements-eu"}
get_claim_foodlaw ~120

Fetch one claim from C.L.A.I.M.S. by its numeric ID (from search_claims_foodlaw). Botanicals are always "on_hold". Usage limit: 2000 calls per user per day (10000 for shared Google network addresses). Example: id 10 (from search_claims_foodlaw).

NameTypeReqDescription
idintegeryesNumeric C.L.A.I.M.S. claim ID from search_claims_foodlaw, e.g. 10.
langstring–Response language: en or pl. Default: en.

No output schema declared.

{"id":10,"lang":"en"}
gis_notification_steps ~83

Step-by-step procedure for notifying a food supplement to the Polish Chief Sanitary Inspectorate (GIS, Art. 29–30 of the Food and Nutrition Safety Act), from the supplemental.pl article. A GIS notification is not a novel food authorisation. Example: lang "en" or "pl".

NameTypeReqDescription
langstring–Response language. Default: en.

No output schema declared.

{"lang":"en"}
novel_food_status ~149

Look up a food or ingredient in the EU Novel Food Catalogue (European Commission data, refreshed weekly): status per part/form (Novel food, Not novel in food, Not novel in food supplements, Authorised novel food, consultation request), with links to Reg. 2015/2283 and the Union list. Example: name "Withania somnifera" or "NMN".

NameTypeReqDescription
langstring–Response language. Default: en.
limitinteger–Max results (default 8, max 20).
namestringyesIngredient name (Latin, English or common name), e.g. "Withania somnifera", "NMN".

No output schema declared.

{"lang":"en","name":"Withania somnifera"}
nutrition_calc ~270

Deterministic nutrition calculation for a recipe (no AI): energy and nutrients per 100 g, micronutrients with %NRV, candidate nutrition claims (withheld if any ingredient is unresolved), allergens and QUID hints. Ingredient lines with mass or volume and the ingredient name in Polish (the food table matches Polish names only; translate other languages first), e.g. "mąka owsiana 500 g", "mleko 200 ml", "miód 50 g". Usage limit: 20 calculations per user per day (500 for shared Google network addresses). Example: ingredients ["mleko 200 ml"] or ["mąka owsiana 500 g", "mleko 200 ml", "miód 50 g"].

NameTypeReqDescription
ingredientsarrayyesOne ingredient per item: Polish ingredient name, quantity and unit (g, kg, mg, ml, l), e.g. "mleko 200 ml".
langstring–Response language. Default: en.
mass_loss_pctnumber–Mass loss during processing (e.g. baking), %.
product_formstring–Default solid.
product_namestring–Optional product/recipe label shown in the result (max 120 chars).

No output schema declared.

{"ingredients":["mleko 200 ml"],"lang":"en","product_form":"solid","product_name":"owsianka"}
search_articles ~130

Full-text search of supplemental.pl knowledge articles on EU/PL food law (health claims, novel food, supplements, labelling, CJEU case law) in Polish, English or German. Returns titles, URLs, dates, summaries and language versions. Example: query "novel food NMN", lang "en".

NameTypeReqDescription
langstring–Response language. Default: en.
limitinteger–Max results (default 5).
querystringyesSearch terms, e.g. "novel food NMN" or "oświadczenia zdrowotne witamina D".

No output schema declared.

{"lang":"en","query":"novel food NMN"}
search_claims_foodlaw ~174

Match an ingredient (and optional dose) against Reg. 432/2012 authorised claims and the SANCO/11074/2013 botanical list via C.L.A.I.M.S. (FOODLAW.ai). Botanical claims are always returned as regulatory_status "on_hold" (not authorised). Usage limit: 2000 calls per user per day (10000 for shared Google network addresses). Example: substance "ashwagandha" or "vitamin C", optional dose "300 mg".

NameTypeReqDescription
dosestring–Optional dose, e.g. "300 mg".
langstring–Response language: en or pl. Default: en.
substancestringyesIngredient (Latin, English or Polish), e.g. "ashwagandha" or "vitamin C".

No output schema declared.

{"lang":"en","substance":"vitamin C"}
Install

How do I install the supplemental.pl — EU/PL food law MCP server?

supplemental.pl — EU/PL food law is a hosted endpoint at https://mcp.supplemental.pl/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 · mcp.supplemental.pl

# add to Claude Code
claude mcp add --transport http pl-supplemental-foodlaw 'https://mcp.supplemental.pl/mcp'
Common questions

What is the supplemental.pl — EU/PL food law MCP server?

supplemental.pl — EU/PL food law is an MCP server listed in the public MCP registry as pl.supplemental/foodlaw. EU/PL food law for supplement firms: health claims, novel food, GIS, C.L.A.I.M.S. Not legal advice. This page covers its hosted endpoint (https://mcp.supplemental.pl/mcp).

Is the supplemental.pl — EU/PL food law MCP server safe to use?

supplemental.pl — EU/PL food law scores 80 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 supplemental.pl — EU/PL food law MCP server expose?

supplemental.pl — EU/PL food law exposes 8 tools: search_articles, get_article, check_health_claim, novel_food_status, search_claims_foodlaw, and 3 more. Their descriptions and schemas cost roughly 1,223 tokens of context every time the server is loaded.

Does the supplemental.pl — EU/PL food law MCP server require authentication?

No. We connected to supplemental.pl — EU/PL food law without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the supplemental.pl — EU/PL food law MCP server still maintained?

supplemental.pl — EU/PL food law is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the supplemental.pl — EU/PL food law MCP server?

VerifyMCP ran 12 checks on supplemental.pl — EU/PL food law, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about supplemental.pl — EU/PL food law: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.