SuppCo is answering right now. Last checked 10 min ago. It exposes 30 tools.
Supplement research, product and brand TrustScores, and your SuppCo stack and Buying Club cart.
Uptime history
26 days of history
26 days agonow
100.0%
Uptime 24h
91 of 91 checks
30
Tools
read from the server
479 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 2
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 October 2026. No other catalogue keeps this.
9 Oct
2 tools changed the parameters they ask for
suppco_get_product_info, suppco_get_product_trust_score
Nothing serious here today
Today is the operative word: we check SuppCo every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
run in your terminal
claude mcp add suppco --transport http https://api.supp.co/mcpSettings → Connectors → Add custom connector, then paste this address
https://api.supp.co/mcp~/.codex/config.toml
[mcp_servers.suppco]
url = "https://api.supp.co/mcp".cursor/mcp.json
{
"mcpServers": {
"suppco": {
"url": "https://api.supp.co/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"suppco": {
"type": "http",
"url": "https://api.supp.co/mcp"
}
}
}Available tools 30
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
suppco
suppco_add_to_cart
Add a Buying Club product to the signed-in user's cart (the same cart as the SuppCo app). Use a product ID or slug from suppco_find_buying_club_products or suppco_compare_to_buying_club; only Buying Club products can be added. Set subscription to true for a recurring subscription at the product's recommended shipping interval. Returns the updated cart. This adds to any quantity already in the cart, so calling it again adds more units; to set an exact quantity, use suppco_update_cart_item.
suppco_add_to_stack
Use this when the user wants to start tracking a product in their SuppCo stack. Adds the product to the signed-in user's stack. `id` is a SuppCo product UUID or slug from a search or product result. This does not buy anything; to buy a Buying Club product, use suppco_add_to_cart.
suppco_compare_product_to_alternatives
Compare a product against alternatives in its category. Returns a detailed view of the anchor product (trust score, ingredients, excipients) alongside filtered alternatives. Use when user asks to compare, find alternatives, or asks "is there something better?"
suppco_compare_to_buying_club
Use this when the user asks whether the SuppCo Buying Club carries an alternative to a specific product, usually one they already take. Returns that product plus Buying Club products in the same category with TrustScore, price, member price and cashback.
suppco_find_brands
Find and filter brands. Use this to search for brands by name or to list brands matching specific criteria (e.g., brands that have been TESTED by SuppCo).
suppco_find_buying_club_products
Open-ended search/browse of the SuppCo buying club catalog: free-text lookups ("Thorne Magnesium") or filtered browsing by category, trust, price, form, certifications, and brand. Every result is a buying-club product with member pricing and earnings credit (cashback). Use this when the user is exploring a category with no specific current product in play. For finding an alternative to a product the user already takes, use suppco_compare_to_buying_club instead (it returns their current product as the anchor).
suppco_find_products
Find products based on user query - handles search, browsing, and recommendations. Use this whenever the user wants to discover or find products.
suppco_get_brand_trust_score
Use this when the user asks how trustworthy or high-quality a specific supplement brand is. Returns the brand's TrustScore with its quality assessment. Pass the brand's name, slug or UUID as brand_query.
suppco_get_checkout_url
Get a secure checkout link for the signed-in user's cart. The link signs the user into checkout so member pricing and credit apply. It works once and expires after 10 minutes, so call this only when the user is ready to pay and give them the link right away. Buying Club credit is applied by default; set use_wallet to false if the user doesn't want to use their credit.
suppco_get_my_cart
Get the signed-in user's Buying Club cart: items, quantities, one-time or subscription, prices, subtotal, available credit and estimated cashback, plus any items that are no longer available.
suppco_get_my_nutrient_plan
Use this when the user asks which nutrients they should take or how much. Returns the signed-in user's personalized plan with recommended nutrients and dosages. For what their current stack actually provides, use suppco_get_my_nutrient_totals.
suppco_get_my_nutrient_totals
Use this when the user asks how much of a nutrient their current supplements provide, or whether they are over or under recommended amounts. Returns the daily nutrient totals from the signed-in user's stack compared with recommended values.
suppco_get_my_protocols
Use this when the user asks about the health protocols they are following. Returns the signed-in user's protocols with progress and supplement recommendations. To find new protocols, use suppco_search_protocols.
suppco_get_my_schedule
Get the user's current supplement schedule — shows when each product is taken (morning, midday, evening, bedtime, workout), dose amounts per time slot, with_food flags, and schedule frequency.
suppco_get_my_stack
Use this when you need the signed-in user's current supplements, for example before recommending, comparing, swapping or removing products. Returns every product in their stack with dosages and daily totals, including the product IDs other SuppCo tools accept.
suppco_get_nutrient_info
Use this when the user asks about dosing for a specific nutrient or supplement: typical daily intake ranges and upper limits from SuppCo's references, timing and whether to take it with food, plus a summary of its graded research. General information only; does not diagnose, treat or give personalized dosing advice. For what studies say about a supplement for a specific health area, use suppco_search_effects.
suppco_get_product_info
Look up detailed information (composition, ingredients, price, format, servings) for one or more specific products by UUID, slug, or name. Use for "tell me about <product>" or to hydrate products you only have ids for (e.g. from the user's stack). Accepts names when you don't have an id yet. For TrustScore rationale, certifications, or testing, call suppco_get_product_trust_score instead.
suppco_get_product_trust_score
Get TrustScore details and quality assessment for one or more products: score rationale/commentary, certifications, testing and verified lab results, brand manufacturing/testing practices, and excipient risk ratings. Accepts product ids/slugs/names (multiple). Call this before discussing why a product is (or is not) trustworthy, its certifications, or its testing — the other product tools return only the headline score number.
suppco_get_stack_score
Use this when the user asks how good their supplement stack is or how to improve it. Returns the signed-in user's StackScore with Quality, Value, Goals and Dosage ratings and coaching recommendations. Pass category to get a single category.
suppco_manage_stack
Legacy: prefer suppco_add_to_stack / suppco_remove_from_stack / suppco_swap_products. Add, remove, or swap products in user's supplement stack using natural language commands.
suppco_refresh_stack_score
Kick off a StackScore refresh. The score recalculates asynchronously and takes a few minutes. Only use when the user confirms they want to refresh.
suppco_remove_from_cart
Remove a product from the signed-in user's cart, or set remove_unavailable to true to clear items that are no longer available. Removing a product removes every cart line for it, one-time and subscription. Returns the updated cart.
suppco_remove_from_stack
Use this when the user has stopped taking a product or wants it off their SuppCo stack. Removes the product from the signed-in user's stack. `id` is a SuppCo product UUID or slug, as shown by suppco_get_my_stack.
suppco_save_memory
Use this when the user explicitly asks SuppCo to remember a preference or fact about them for future SuppCo conversations. Saves one short note to their SuppCo account.
suppco_search_effects
Use this when the user asks what published research says about a supplement: its overall effects, or whether it does something for a specific health area such as heart health, stress or focus. Also use it when the user asks which supplements have the most research behind them for a health area. Returns SuppCo's summaries of published studies with evidence grades. General information only; does not diagnose, treat or recommend treatment for any condition. For dosing and nutrient basics, use suppco_get_nutrient_info; for a full supplement routine for a goal, use suppco_search_protocols.
suppco_search_protocols
Use this when the user asks for a supplement protocol for a health goal, such as sleep, energy or weight loss. Searches SuppCo's protocols and returns the matches. For protocols the user already follows, use suppco_get_my_protocols.
suppco_swap_products
Use this when the user wants to replace a product in their stack with a different one, for example after comparing alternatives. Removes old_product_id from the stack and adds new_product_id. Both are SuppCo product UUIDs or slugs.
suppco_update_cart_item
Set the quantity of a product that is already in the signed-in user's cart. quantity is the new total, not an amount to add, so repeating the call is safe; 0 removes the item. If the product is in the cart as both a one-time purchase and a subscription, set subscription to choose which one to change. Returns the updated cart.
suppco_update_my_profile
Use this when the user gives profile details they want saved: age, sex, health goals, dietary preferences, experience level, buying preference, preferred form or biggest challenge. Only the fields you pass are changed, and each one replaces the stored value. Saved preferences change the defaults other SuppCo tools use, such as product search ranking.
suppco_update_product_schedule
Use this when the user wants to change when or how they take a product that is already in their stack. Replaces that product's schedule: time-of-day amounts, daily, specific-days or every-other-day timing, as-needed, with food, and timing notes.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.supp.co/mcp | streamable-http | answering | 481 ms | 10 min ago |
Alternatives to SuppCo
same job, measured the same waySuperCheap
by hardtab
Search products, manage a customer cart, and request current checkout quotes.
Portage Store
by tomtom87
Shopify catalog search and product lookup via MCP; the Portage CLI adds full agentic buying.
RoboTrunk
by robotrunk
Search independent stores, check recalls and product facts, and prepare checkout at the store.
buyer.sh
by buyer
Product search for agents: price, merchant, rating and checkout links across online stores.
Okun Koneosa
by okunkoneosa
Finnish industrial supplies store. Read-only MCP: catalog search, product details, cart, policies.
AutoID Product Catalog & Support
by autoid
Read-only AutoID Romania MCP for product search, live stock/prices, specs, and technical support.
Continente MCP
by andredelgado
Unofficial Continente.pt shopping: search products, read favorites and orders, manage the cart.
Picnic
by mrvdh
Search products, fill the cart and pick a delivery slot at the online supermarket Picnic
SuppCo — questions
Answers built from our own checks of this server.
What can SuppCo do?
It exposes 30 tools, read directly from the server on our last check. Among them: suppco_add_to_cart, suppco_add_to_stack, suppco_compare_product_to_alternatives, suppco_compare_to_buying_club, suppco_find_brands, suppco_find_buying_club_products and 24 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is SuppCo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 479 ms. The bar chart above shows every period we have measured.
How do I connect SuppCo?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SuppCo need an API key?
No. SuppCo completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 30 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SuppCo?
It answers our handshake in 479 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.