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.

Verateca

REMOTE · VERATECA.COM

Dietary supplement register: compositions, country upper limits, US prices, stack check vs limits.

Available components

+3 this week 77 Trust /100

Last scanned (19 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 4 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 Security74
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 847 tokens (~141/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 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.

  • 3 Nov 26 +1
    • Schema quality: 161 → 141 ▲ functional
    • “check_stack” reworded the description of “country” cosmetic
    • “compare_products” reworded the description of “country” cosmetic
    • “get_ingredient” reworded the description of “country” cosmetic
    • “get_product” reworded the description of “country” cosmetic
    • “get_selection_link” reworded the description of “country” cosmetic
    • “search_products” reworded the description of “country” cosmetic
  • 2 Nov 26 −1
    • Tool “compare_products” rewrote its description, which is the text the model reads security
    • Tool “get_product” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
    • “compare_products” added an optional parameter “period_days” cosmetic
    • “get_product” added an optional parameter “period_days” cosmetic
  • 1 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.

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 27 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
    • “get_product” reworded the description of “country” cosmetic
  • 25 Oct 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.

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 4 Nov 2026 · Probed https://verateca.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=verateca.com CN=WE1,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 d1db88fc30bad5020e92711a1aa24f74
SANs: verateca.com, mailbox.verateca.com, *.mailbox.verateca.com
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 insecure

Validation of verateca.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
verateca.com. 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
Header Value
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://verateca.com/mcp Verified 200
http (plaintext) http://verateca.com/mcp HTTPS enforced 308 https://verateca.com/mcp
MCP tools · 6 exposed · ~847 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_stack ~139

Adds up each ingredient across several products taken together (up to 12) and compares each daily total with the adult upper limit of the country, with the same rules engine as the Verateca site. For every ingredient: total per day, applicable limit, share of the limit, status ("within the upper limit", "over the upper limit", "no upper limit set" or "not compared"), the products that contribute, and duplicates across products. Limits of other countries follow. Interactions with medicines are not checked.

NameTypeReqDescription
countrystring–The United States is the only market currently available.
itemsarrayyesProducts taken together.

No output schema declared.

No examples provided.

compare_products ~135

Puts 2 to 6 published products side by side: daily dose, rounded daily price plus verified exact pack basis where available, and for each ingredient the daily amount, effective comparison denominator and percentage. Canonical reference maxima can differ from the effective denominator when age is unknown.

NameTypeReqDescription
countrystring–The United States is the only market currently available.
idsarrayyesProduct ids, e.g. ["US:302778", "US:217710"].
period_daysinteger–Optional days of consumption, calculated from verified pack and daily-use basis. This is not a whole-pack checkout price.

No output schema declared.

No examples provided.

get_ingredient ~121

Returns one substance of the register: its forms with the share of the element where known, the upper limit of the country first, then the limits of other countries with type, source and the date checked, reference sources, and the number of published products that contain it.

NameTypeReqDescription
countrystring–The United States is the only market currently available.
idstring–Substance id, e.g. "magnesium", "vit_d".
namestring–Substance name, e.g. "Vitamin D", as an alternative to id.

No output schema declared.

No examples provided.

get_product ~161

Returns one published product record: source-recorded composition with printed-disclosure verification status, daily amounts, a cohesive comparison with effective denominator, age policy, scope and percentage, and separate reference limits of other countries, the status in the country, prices per day where published, and the dates of each part.

NameTypeReqDescription
countrystring–The United States is the only market currently available.
idstring–Verateca product id, e.g. "US:302778", as returned by search_products.
period_daysinteger–Optional days of consumption, calculated from verified pack and daily-use basis. This is not a whole-pack checkout price.
urlstring–Verateca product page address, as an alternative to id.

No output schema declared.

No examples provided.

get_selection_link ~167

Returns the address of the Verateca order page for one of its three paid services (quick, full, review), with the price and currency the site shows for the country and a one-line description. The tool takes no payment and creates no order; the order page asks its own questions and takes payment there.

NameTypeReqDescription
countrystring–The United States is the only market currently available.
goalsarray–Optional goals to preselect on the order page (quick: 1, full: up to 3; ignored for review). They travel sealed, not in plain words.
servicestringyesquick: up to three products for one goal; full: one set for up to three goals; review: a written review by a Verateca specialist.

No output schema declared.

No examples provided.

search_products ~124

Searches the Verateca register of dietary supplements by product name, brand, ingredient or barcode. Returns up to 10 published products with id, brand, form, page address, lowest price per day where prices are published, number of offers and the date the record was checked. Results are ordered by match, never by payment.

NameTypeReqDescription
countrystring–The United States is the only market currently available.
limitinteger–Number of results, 1–10.
querystringyesProduct name, brand, ingredient or barcode (UPC/EAN).

No output schema declared.

No examples provided.

Install

How do I install the Verateca MCP server?

Verateca is a hosted endpoint at https://verateca.com/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 · verateca.com

# add to Claude Code
claude mcp add --transport http a1476-verateca 'https://verateca.com/mcp'
Common questions

What is the Verateca MCP server?

Verateca is an MCP server listed in the public MCP registry as io.github.a1476/verateca. Dietary supplement register: compositions, country upper limits, US prices, stack check vs limits. This page covers its hosted endpoint (https://verateca.com/mcp).

Is the Verateca MCP server safe to use?

Verateca scores 77 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 Verateca MCP server expose?

Verateca exposes 6 tools: search_products, get_product, get_ingredient, check_stack, compare_products, get_selection_link. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.

Does the Verateca MCP server require authentication?

No. We connected to Verateca without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Verateca MCP server still maintained?

Verateca is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.