MCP servers › co.supp › suppco

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

co.supp/suppco

Supplement research, product and brand TrustScores, and your SuppCo stack and Buying Club cart. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: commerce-and-marketing · AI-classifiedversion 2.0.0streamable HTTP30 tools

Summary

co.supp/suppco is a remote MCP server listed in the official MCP registry at version 2.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 30 tools, 0 resources and 5 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 30
Described as changing data: 11 of 30 toolsAI-classified
Mainly works on: accounts and data in outside web servicesAI-classified
Topic: commerce-and-marketingAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 10 tools whose name or declaration suggests they change data (suppco_update_product_schedule, suppco_update_my_profile, suppco_save_memory, suppco_add_to_stack, suppco_remove_from_stack and 5 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

11 tools are described as changing something (suppco_update_product_schedule, suppco_update_my_profile, suppco_save_memory, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 2.0.0, published 2026-10-09 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-09 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-22
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 2.0.0 (published 2026-10-09).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

30tools

0resources

5prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

11 of 30 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

suppco_find_productsreads or searches
“Find products based on user query - handles search, browsing, and recommendations.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
13 inputs
- querystring“Free text search for a specific product by name (e.g., "Thorne Creatine", "AG1 Greens").”
- product_category_namestring“REQUIRED for all non-query searches.”
- include_ingredientsstring“Comma-separated list of ADDITIONAL ingredients the product must also contain beyond its category (e.g., for 'collagen with hyaluronic acid', set product_catego…”
- exclude_ingredientsstring“Comma-separated list of ingredients the product must NOT contain (e.g., 'stevia,sucralose').”
- prioritystring“How to rank results.”
- certificationsstring“Required certifications, comma-separated.”
- brandstring“The brand a user prefers”
- max_pricenumber“Maximum price in dollars (e.g., 50.00)”
- servingsstring“Comma-separated list of serving counts (e.g., '30,60,90')”
- formstring“Comma-separated list of product forms.”
- testedboolean“When true, only return products that have been TESTED by SuppCo (identity, potency, and/or heavy metals testing performed by SuppCo's lab)”
- limitinteger“Maximum number of products to return (default: 5, max: 50)”
- offsetinteger“Number of products to skip for pagination (default: 0)”
suppco_get_product_inforeads or searches
“Look up detailed information (composition, ingredients, price, format, servings) for one or more specific products by UUID, slug, or name.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- productsstring or arrayrequired“One or more product identifiers (max 5): an array of strings, or one string separated by ' | '.”
suppco_get_product_trust_scorereads or searches
“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 excipi…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- productsstring or arrayrequired“One or more product identifiers (max 5): an array of strings, or one string separated by ' | '.”
suppco_compare_product_to_alternativesreads or searches
“Compare a product against alternatives in its category.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 1 required
- product_id_or_slugstringrequired“Product ID (UUID), slug, or product name of the product to compare.”
- prioritystring“How to rank alternatives.”
- certificationsstring“Certifications filter, comma-separated.”
- max_pricenumber“Maximum price in dollars”
- servingsstring“Comma-separated serving counts (e.g., '60,90')”
- formstring“Product forms.”
suppco_find_buying_club_productsreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
11 inputs
- querystring“Free-text search for a specific product by name (e.g., "Thorne Creatine").”
- product_category_namestring“The supplement category to browse (e.g., 'Vitamin D', 'Magnesium', 'Creatine').”
- prioritystring“How to rank results.”
- certificationsstring“Required certifications, comma-separated.”
- brandstring“Restrict to a specific brand.”
- max_pricenumber“Maximum price in dollars (e.g., 50.00).”
- servingsstring“Comma-separated serving counts (e.g., '30,60,90').”
- formstring“Comma-separated product forms.”
- testedboolean“When true, only products TESTED by SuppCo.”
- limitinteger“Max products to return (default: 5, max: 24).”
- offsetinteger“Number of products to skip for pagination (default: 0).”
suppco_compare_to_buying_clubreads or searches
“Use this when the user asks whether the SuppCo Buying Club carries an alternative to a specific product, usually one they already take.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 1 required
- product_id_or_slugstringrequired“The product to compare against the Buying Club — usually one the user already takes (e.g.”
- prioritystring“How to rank alternatives.”
- certificationsstring“Required certifications, comma-separated.”
- max_pricenumber“Maximum price in dollars.”
- servingsstring“Comma-separated serving counts (e.g., '30,60,90').”
- formstring“Comma-separated product forms.”
suppco_get_brand_trust_scorereads or searches
“Use this when the user asks how trustworthy or high-quality a specific supplement brand is.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
- brand_querystring“Brand UUID, slug, or name (ex: '80a5d287-8ec2-4b61-9004-10103da1133d', 'life-extension', 'Life Extension')”
- brand_namestring“Deprecated alias of brand_query”
suppco_find_brandsreads or searches
“Find and filter brands.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
- namestring“Search for a brand by name (e.g., "Thorne", "Garden of Life").”
- testedboolean“When true, only return brands that have participated in TESTED by SuppCo (independent lab testing for identity, potency, and heavy metals)”
suppco_search_effectsreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
- health_conditionstring“The health area or outcome to look up (e.g., "Heart Health", "Bone & Joint Health", "Focus and Attention").”
- supplement_namestring“The supplement name (e.g., "Fish Oil", "Magnesium").”
suppco_get_nutrient_inforeads or searches
“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 …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- nutrient_namestringrequired“The name of the nutrient or supplement (e.g., 'Vitamin D3', 'Magnesium', 'Fish Oil')”
suppco_search_protocolsreads or searches
“Use this when the user asks for a supplement protocol for a health goal, such as sleep, energy or weight loss.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- querystringrequired“Query (e.g., 'Protocol for weight loss')”
suppco_get_my_stackreads or searches
“Use this when you need the signed-in user's current supplements, for example before recommending, comparing, swapping or removing products.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.

Show 18 more tools

suppco_get_my_schedulereads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
suppco_update_product_schedulecreates or changes datadescribed as changing data
“Use this when the user wants to change when or how they take a product that is already in their stack.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
9 inputs, 2 required
- product_idstringrequired“Product slug or UUID”
- schedulestringrequired“JSON array of time-slot assignments, e.g.”
- as_neededstring“Whether the product is taken as needed (true/false).”
- with_foodstring“Whether the product should be taken with food (true/false).”
- change_daily_amountstring“Set true ONLY when the user asked to change how many units they take per day.”
- schedule_typestring“Schedule type: daily, specific_days, or every_other_day”
- schedule_daysstring“Array of day names (e.g.”
- every_other_day_startstring“When to start every_other_day schedule: "today" or "tomorrow"”
- schedule_notesstring“Brief timing instructions that the schedule cannot capture (e.g., "take 2 hours apart from calcium", "take on empty stomach 30 min before bed").”
suppco_get_my_nutrient_planreads or searches
“Use this when the user asks which nutrients they should take or how much.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
suppco_get_my_nutrient_totalsreads or searches
“Use this when the user asks how much of a nutrient their current supplements provide, or whether they are over or under recommended amounts.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
suppco_get_my_protocolsreads or searches
“Use this when the user asks about the health protocols they are following.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
suppco_update_my_profilecreates or changes datadescribed as changing data
“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.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
8 inputs
- ageinteger“User's age in years (integer between 13 and 150)”
- sexstring“User's biological sex (valid options: male, female, intersex, not_specified)”
- biggest_challengestring“User's biggest challenge with supplements (free text)”
- dietary_preferencesarray“User's dietary preferences as an array”
- expertisestring“User's experience level with supplements (valid options: Beginner, Routine, SuperUser)”
- buying_preferencestring“User's supplement buying preference (valid options: Highest quality available, Best value, Most affordable)”
- preferred_formstring“User's preferred supplement form (valid options: Single Ingredient, Blends, Both)”
- health_goalsarray“User's health goals as an array, CSV string, or single string (valid options: Bone & Joint, Cardiovascular, Cognition, Detox, Energy, Essential Health, Fertili…”
suppco_save_memorycreates or changes datadescribed as changing data
“Use this when the user explicitly asks SuppCo to remember a preference or fact about them for future SuppCo conversations.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
- memorystringrequired“The note to remember”
suppco_add_to_stackcreates or changes datadescribed as changing data
“Use this when the user wants to start tracking a product in their SuppCo stack.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
- idstringrequired“SuppCo Product ID”
suppco_remove_from_stackdeletesdescribed as changing data
“Use this when the user has stopped taking a product or wants it off their SuppCo stack.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
- idstringrequired“SuppCo Product ID”
suppco_swap_productscreates or changes datadescribed as changing data
“Use this when the user wants to replace a product in their stack with a different one, for example after comparing alternatives.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
2 inputs, 2 required
- old_product_idstringrequired“SuppCo Product ID to remove”
- new_product_idstringrequired“SuppCo Product ID to add”
suppco_manage_stackcreates or changes datadescribed as changing data
“Legacy: prefer suppco_add_to_stack / suppco_remove_from_stack / suppco_swap_products.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
- action_descriptionstringrequired“Natural language stack action.”
suppco_get_stack_scorereads or searches
“Use this when the user asks how good their supplement stack is or how to improve it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- categorystring“Optional category filter: 'quality', 'value', 'goals', or 'dosage'.”
suppco_refresh_stack_scoredescribed as changing data
“Kick off a StackScore refresh.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
Takes no inputs.
suppco_add_to_cartcreates or changes datadescribed as changing data
“Add a Buying Club product to the signed-in user's cart (the same cart as the SuppCo app).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 1 required
- product_id_or_slugstringrequired“SuppCo product ID (UUID) or slug of a Buying Club product.”
- quantityinteger“Number of units to add (default 1).”
- subscriptionboolean“true to subscribe (recurring delivery), false for a one-time purchase (default false).”
suppco_update_cart_itemcreates or changes datadescribed as changing data
“Set the quantity of a product that is already in the signed-in user's cart.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
3 inputs, 2 required
- product_id_or_slugstringrequired“SuppCo product ID (UUID) or slug of a product in the cart, as shown by suppco_get_my_cart.”
- quantityintegerrequired“New total number of units for this item.”
- subscriptionboolean“true to change the subscription item, false for the one-time item.”
suppco_remove_from_cartdeletesdescribed as changing data
“Remove a product from the signed-in user's cart, or set remove_unavailable to true to clear items that are no longer available.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
2 inputs
- product_id_or_slugstring“SuppCo product ID (UUID) or slug of the product to remove, as shown by suppco_get_my_cart.”
- remove_unavailableboolean“true to remove every item that is no longer available (the stale items suppco_get_my_cart lists).”
suppco_get_my_cartreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
suppco_get_checkout_urlreads or searches
“Get a secure checkout link for the signed-in user's cart.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input
- use_walletboolean“Apply the user's Buying Club credit to this order (default true).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 30 tools
Says what it returns: 77% of 30 tools
States limits, defaults or errors: 43% of 28 tools
Says when to use it: 100% of 30 tools
Items covered per tool: 3.2 of 4 on average

Counted from the listing

Parameters with a description: 100% of 79
Tools with a description: 100% of 30
Typical description length: 280 characters

The tool set

Counted from the listing

Tools: 30
Size of the list: about 10,544 tokens for an agent to load (characters ÷ 4)
Naming: 30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 30 of 30 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://api.supp.co/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "suppco": {
      "url": "https://api.supp.co/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "suppco": {
      "type": "http",
      "url": "https://api.supp.co/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"suppco","type":"http","url":"https://api.supp.co/mcp"}'

Claude Code

claude mcp add --transport http suppco https://api.supp.co/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.supp.co/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint api.supp.co/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about co.supp/suppco

Answered from the data above

Is co.supp/suppco safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 11 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does co.supp/suppco need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has co.supp/suppco been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can co.supp/suppco do?

It lists 30 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and delete. We did not call any tool, so this describes the text, not the behaviour.

Can co.supp/suppco change or delete data?

11 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.LetsFG/letsfgLetsFG — Flights & Hotelsalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.avansaber/seo-monsteralso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.mgwalkerjr95/texas-groceryalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.ilyautov/marketplaces-mcp-ruMarketplaces MCP (RU) — Wildberries, Ozon, Yandex Market, Avitoalso has tools that creates or changes data, deletes, reads or searchescompare with this one
com.mcparmory/apolloalso has tools that creates or changes data, deletes, reads or searchescompare with this one
com.mcparmory/customerio-journeys-trackalso has tools that creates or changes data, deletes, reads or searchescompare with this one

Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,185 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 30 tools, 0 resources, 5 prompts.
6,774 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

commerce-and-marketing

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The pages we read do not state how the product is priced.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

logging, prompts, resources, tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “co.supp/suppco: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/co.supp/suppco

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/co.supp/suppco)](https://protocolprobe.com/mcp/servers/co.supp/suppco)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology