Gemalli B2B Trade
REMOTE · GEMALLI.COM
Global B2B trade: verified manufacturers, product search, sanctions screening, HS codes.
Available components
Last scanned (22 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
Recent critical change
Authorization (27 Oct 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (remember_about_person). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5883 tokens (~210/item across 28 items; 28 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “answer_request_question” functional
- New tool “get_request_status” functional
- New tool “post_request” functional
- 30 Oct 26 −1
- Tool “get_product” rewrote its description, which is the text the model reads security
- Tool “list_manufacturers” rewrote its description, which is the text the model reads security
- Tool “search_products” rewrote its description, which is the text the model reads security
- 27 Oct 26 −7
- Authorization: partial → fail ▼ critical
- New tool “remember_about_person”, which the server declares destructive security
- Tool “get_feedback_reasons” rewrote its description, which is the text the model reads security
- Tool “list_manufacturers” rewrote its description, which is the text the model reads security
- Tool “search_products” rewrote its description, which is the text the model reads security
- Schema quality: 160 → 206 ▼ functional
- New tool “get_agent_knowledge” functional
- New tool “get_person_memory” functional
- New tool “rate_agent_result” functional
- 16 Oct 26 0
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “answer_request_question” was removed ▼ security
- Tool “get_request_status” was removed ▼ security
- Tool “post_request” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 3888 → 3377 ▲ functional
- 14 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 3377 → 3888 ▼ functional
- New tool “answer_request_question” functional
- New tool “get_request_status” functional
- New tool “post_request” functional
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://gemalli.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gemalli.com | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d0155dd832d90e9cb60caf0000f9844a97 |
| SANs: gemalli.com, www.gemalli.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gemalli.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| gemalli.com. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gemalli.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://gemalli.com/api/mcp | HTTPS enforced | 301 | https://gemalli.com/api/mcp |
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 →
add_feedback_message Add to a request ~95
Add a message to an existing feedback ticket of the current visitor — when they remember a detail ("only in Chrome") after the ticket was created. Do NOT create a second ticket for the same problem. Identity comes from the visitor pass; a ticket that is not theirs is simply not found.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What the person wants to add |
| ticket_id | string | yes | ticket_id returned by create_feedback_ticket |
No output schema declared.
No examples provided.
answer_request_question Answer a request question ~97
Answer the clarifying questions on a request posted with post_request, when get_request_status shows "needs_info". Use the person's own answer. Pass the same email used to post it (not needed when signed in as the author).
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The person's answer to the questions. |
| string | – | The email the request was posted with. | |
| request_code | string | yes | The request_code returned by post_request. |
No output schema declared.
No examples provided.
check_dual_use Dual-use check ~103
Check whether an HS customs code falls under EU dual-use export controls (Regulation 2021/821 and equivalents), optionally for a specific destination country. A match means the goods may need an export licence. Use it after lookup_hs_code, before the person commits to a shipment.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Destination country (ISO-2). |
| hs_code | string | yes | HS code from lookup_hs_code. |
| locale | string | – | – |
No output schema declared.
No examples provided.
check_sanctions Sanctions screening ~129
Screen a company or a person against consolidated sanctions, politically-exposed-person and law-enforcement lists (EU, US, UK, UN, Ukraine), sourced from OpenSanctions. Returns possible matches with a similarity score. Use it before the person commits to a counterparty. Treat a match as a reason to verify further, not as proof.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2. |
| limit | integer | – | Defaults to 10. |
| query | string | yes | Name, alias, or company string to screen. |
| topic | string | – | – |
No output schema declared.
No examples provided.
close_feedback_ticket Close a request ~85
Close a feedback ticket of the current visitor when they say it is no longer relevant or they worked it out. A ticket the team already finished (fixed or declined) is NOT closed — say so instead. Identity comes from the visitor pass.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Optional: why they close it |
| ticket_id | string | yes | ticket_id returned by create_feedback_ticket |
No output schema declared.
No examples provided.
create_feedback_ticket Send feedback ~215
Record a feedback ticket for the Gemalli team: a question, a problem or a suggestion. Call it ONCE, only after the person confirmed the wording you read back to them. Identity is taken from the visitor pass — never pass a user id. For a visitor who is not signed in, contact_email is required: without it there is no way to tell them it was fixed.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | Required when the visitor is not signed in |
| kind | string | yes | question = asks something · bug = something is broken · idea = suggestion |
| locale | string | yes | Language to answer in, e.g. ru / uk / en |
| message | string | yes | The request in the person’s own words |
| page_url | string | – | Platform page the person was on |
| subject | string | yes | Short summary as you understood it |
| transcript | array | – | Last turns of the conversation (max 20 turns / 8000 chars; longer is trimmed, not rejected) |
No output schema declared.
No examples provided.
get_agent_knowledge Agent knowledge ~351
Platform rules for the agent, as short lines to put into your prompt. Call it once and cache it by `rev`; re-read when the platform pokes you or when your fallback poll comes due. Without `ids` you get ALL active rules for the audience, short form only — YOU pick which ones belong in a given answer (no more than three fit a prompt). With `ids` you get the full text of those rules instead, including RETIRED ones, flagged `retired: true` — so your log of «which rules were in this answer» stays readable after a rule is switched off weeks later. Ask for up to 50 ids at once: three is what fits a PROMPT, a review screen needs more. off. A retired rule must never go back into a prompt. If this door is silent, answer without rules: that is the normal state and must change nothing in your behaviour.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Which agent asks. Defaults to widget. Rules marked for both arrive in either case. |
| ids | array | – | Ids of rules whose FULL text you need — up to 50 per call (that is a review screen, not the whole knowledge base; call without `ids` for all active rules). Retired rules are returned too, flagged. An… |
No output schema declared.
No examples provided.
get_buyer_search_offer Buyer-search packages and prices ~265
Read the buyer-search package offer — what the person buys in the «find buyers» order window: plans with prices in USD, company quotas, country limits, top-up rules, roles, the order stages and — for an HS code — the clarifying question and the buyer segments that fit each answer. These are prices of the BUYER-SEARCH PACKAGE, shown openly in the order window; they are not Gemalli subscription plans, so the get_subscription_plans rule about never stating prices does not apply here. Use it in the sales chat to answer questions and to suggest a plan and segments. You only suggest: the person chooses and pays in the order window, never through you. Right now it is a demo — payment is a test with no charge, company search and emails are switched off — say so plainly and never promise buyers: a company becomes a buyer only by answering. Texts come in the call locale (uk, ru, en; others fall back to en).
| Name | Type | Req | Description |
|---|---|---|---|
| hs_code | string | – | HS code of the product from the page context (2 to 10 digits) — picks the clarifying question and the segments. |
| locale | string | – | Language of the texts: uk, ru or en (others fall back to en). |
No output schema declared.
No examples provided.
get_feedback_reasons Feedback reasons ~250
Reasons a person can pick after rating the agent. Call it once when the widget opens and cache it; re-read when the platform says the dictionary changed, or lazily by the `rev` value. Two lists: `reasons` are the live ones to draw in the window, `retired` are switched off and are only there so old feedback stays readable. 🔴 `label` is the best text WE have for the asked language and may fall back (`lang` says to what). `source_label` is what the admin actually WROTE and `source_lang` is the language they wrote it in — translate from THAT, never from `label`: translating our fallback would make a translation of a translation, losing a little at every step. When a card is shown untranslated, send `reason_shown_lang` with the rating so a reason picked blindly can be told from one picked on purpose. If this door is silent, show the free-text field anyway and still count the thumb — never drop a rating.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the person, e.g. ru / uk / de-AT. Falls back exact → base → English, never Russian. |
No output schema declared.
No examples provided.
get_feedback_thread Open a request ~83
Read one feedback ticket of the current visitor with its whole conversation: the original request, what they added later and what the team answered. Use it to SHOW the ticket, not to decide anything — the team answers, the agent does not answer on their behalf. Identity comes from the visitor pass.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | string | yes | ticket_id returned by create_feedback_ticket |
No output schema declared.
No examples provided.
get_manufacturer Producer profile ~82
Fetch one manufacturer's full profile: company description, country, certifications, and the identifiers of the same profile in other languages. Use it after list_manufacturers or search_products, when the person wants to know who the supplier is.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Locale for the returned translation. |
| slug | string | yes | Manufacturer slug (per-locale or base). |
No output schema declared.
No examples provided.
get_person_memory What we remember about the person ~200
What the platform remembers about THIS person between conversations: up to six stable traits (role, industry, where they ship to, language, attitude to price, document requirements) and the one-line outcome of their last 5 conversations. Call it before you answer, so you do not ask again what they already told you. The person is taken from the visitor token — never pass an id. A guest gets an empty answer (`reason: "guest"`): we keep no memory without a cabinet where the person could see it. Nothing is carried over when a guest signs in — there was nothing to carry — but the account may already hold memory from earlier visits, so call this door again right after sign-in. Each trait carries `origin`: `human` means they said it outright, `model` means an agent inferred it — treat an inferred trait as a guess worth confirming, not as a fact. If this door is silent, answer as before.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_product Product details ~192
Fetch one product's trade terms: minimum order quantity, lead time, Incoterms, HS code, packaging, price range, photos and the supplier it belongs to. `delivery_terms` lists the delivery bases the seller confirmed as {incoterm, place_kind, place_city}: place_kind is seller_site | port | border | buyer_site (null when not stated), place_city is the city name in the requested language (English fallback) or null; an empty list means Incoterms on request. `specs_display` carries the product characteristics ALREADY IN THE REQUESTED LANGUAGE ({key, label, value}) — retell those, never copy the raw `specs` tokens. Use it once the person has picked a product from search_products and wants the terms.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Locale for the returned translation. |
| slug | string | yes | Product slug (per-locale or base). |
No output schema declared.
No examples provided.
get_request_status Check request status ~83
Status of a request posted with post_request: validating, needs_info (with the questions to ask the person), published (with the public link), rejected (with a short note). Pass the same email used to post it.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The email the request was posted with. | |
| request_code | string | yes | The request_code returned by post_request. |
No output schema declared.
No examples provided.
get_subscription_plans Plans and prices ~134
Explain how to get Gemalli pricing. Gemalli does NOT publish plan prices through this API: quotes are given by the sales desk, because what a manufacturer pays depends on their catalogue, languages and markets. Call this when the person asks what Gemalli costs, then give them the contacts you get back and offer to introduce them. Do NOT state, estimate, guess or recall any price, plan tier, discount or limit for Gemalli itself — you do not have that information, and inventing it misleads the person. Prices of goods listed BY manufacturers are a different thing and stay available through the catalogue tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_viewer Who you are ~240
Report who the person is currently acting for on Gemalli: role, interface language and, when signed in, the company they represent and their plan. An anonymous person is a valid answer and comes back as a guest, not an error. If the person signed in after talking to you anonymously, previous_guest carries the identifier of that earlier conversation so you can carry the history over, and linked_at separates a link you have not seen before from one you have already handled. credits tells whether platform credits are on (enabled), the balance and total granted when signed in, buy_url (null means no payment page yet: send the person to Office Live) and action_costs, the only map from a tool to its action and price: call something free only when its credits is 0, never offer an action whose credits is null. wallets carries one entry per credit kind with its balance and low: low true means that kind is running out and the panel should show the remaining-credits note. Every paid answer carries the same wallets, freshly counted after the charge — prefer those over this first reading. Never returns another party's data and never returns secrets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories Product categories ~61
List the product categories on Gemalli with their names in the requested language. Use it to offer the person a choice of category before searching, or to turn a category name into the identifier search_products expects.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Locale for the returned names. |
No output schema declared.
No examples provided.
list_manufacturers Browse producers ~241
List verified manufacturers published on Gemalli. Returns each producer's name, country, certifications and profile identifier in the requested language, newest first. USE THIS whenever the question is about COMPANIES rather than goods: "who makes X", "which factories/producers/suppliers are on the platform", "show me manufacturers from <country>". A question about companies stays this tool even when it names a product — search_products returns goods, not the companies behind them. To find a specific product or filter goods by country, use search_products. RESPONSE SIZE: `count` is how many are in THIS response, `total` is how many exist. When `has_more` is true you have seen only the first `count` of `total` — either call again with a larger `limit` (up to 50) or tell the person you checked the first N of M. Never conclude that a company or product type is absent from the platform from a partial list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (1–50). Defaults to 12. |
| locale | string | – | Preferred locale for returned text. Defaults to "en". |
No output schema declared.
No examples provided.
list_my_feedback My feedback ~56
List the feedback tickets of the current visitor for the Workspace tab. Identity comes from the visitor pass; a guest is matched by the conversation label, so the same person on another device sees nothing — that is expected, not a fault.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_site_sections Site sections ~79
List the pages of gemalli.com you can direct this person to, with the label in their language and the address. Use it before offering a link, so you point at a page that exists rather than guessing. Which pages appear depends on whether the person is signed in.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for the labels. Defaults to English. |
No output schema declared.
No examples provided.
lookup_hs_code HS code lookup ~114
Find the Harmonised System (HS) customs code for a product, by description or by code prefix. Returns matching codes with their official names in the requested language, the chapter they belong to, and a similarity score. Use it when the person needs a customs classification for an import, an export or a quote, then pass the code to check_dual_use.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Defaults to 10. |
| locale | string | – | – |
| query | string | yes | Product description or HS code prefix. |
No output schema declared.
No examples provided.
partnership_inquiry Partnership & investment ~89
Return Gemalli's partnership and investment terms and the founder's direct contact. Use it when the person represents a company that would work with a trade platform rather than buy on it — for example logistics, customs, trade finance, insurance, inspection, an ERP vendor or an investor. It returns information only and sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Company or platform the person represents, if known. |
No output schema declared.
No examples provided.
post_request Post a buying request ~262
Gemalli request board: post what you need to buy (product, quantity, destination); verified manufacturers worldwide reply with quotes within days. Free to post. Pass the person's own words and their real email (ask them, never invent one). Returns a request_code with status "validating"; call get_request_status shortly after — if it says "needs_info", ask the person the questions and send the answer with answer_request_question. The person receives an email to confirm the request.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Name of the agent or platform sending this, e.g. "Claude" — recorded as the source. |
| company | string | – | Their company name, if known. |
| country | string | – | ISO 3166-1 alpha-2 country of the buyer company. |
| string | – | The person's real email — confirmation and replies go there. Not needed if you are signed in as the buyer. | |
| locale | string | – | Language of the request, e.g. "en". |
| name | string | – | The person's name, as they gave it. |
| text | string | yes | What they want to buy, in their words: product, quantity, destination, terms. |
| website | string | – | Company website, if known. |
No output schema declared.
No examples provided.
rate_agent_result Rate the agent ~680
Record what a person thought of something the agent produced — a reply, an export, a report, an email. Send it as soon as they press the thumb: the reason and their words are optional and may follow in a second call, which replaces the first. Pick `reason_code` from get_feedback_reasons; an unknown code is dropped and the rating is still saved (`reason_dropped: true`). For `target_kind: "report"` the `target_ref` is the view_key, NOT the report_key — one report is read by many country pages and only the view_key tells them apart. `target_ref` is verified against your own message log: the answer carries `ref_check` saying whether it matched (`verified`), did not (`mismatch`), could not be checked (`unchecked`) or was never sent (`absent`). A rating is never dropped because the check failed.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Their own words. Optional. Trimmed at 2000 characters. |
| knowledge_ids | array | – | Ids of the platform rules that were in the prompt for this answer, up to 50. This is how a harmful rule gets noticed from a single complaint. |
| model | string | – | Which model produced the rated answer. |
| probe | boolean | – | True when the call comes from a test run rather than a person. 🔴 Derive it from the process you run in — do not set it by hand: a flag someone has to remember is a flag someone forgets. The rating i… |
| reason_code | string | – | A code from get_feedback_reasons. |
| reason_shown_lang | string | – | Language the person actually SAW the reason card in — send it together with `reason_code`, never alone. It exists so that "they picked this reason" can be told apart from "they tapped something they… |
| signal | string | – | thumb (default) for a pressed thumb; undone when they cancelled the result; rephrased or left for the quiet signals. The weight is set by the platform, not by you. |
| surface | string | yes | Where it happened, e.g. widget. |
| target_kind | string | yes | What was rated: answer | export | report | email | any future kind. |
| target_ref | string | – | Your identifier of the rated work: the message id for an answer, the view_key for a report. Omit it only when the kind has none. |
| topic | string | – | What the exchange was about, one short phrase. |
| verdict | string | yes | The thumb the person pressed. Send "retracted" (or an empty string) when they pressed the same thumb again and took the rating back — it then stops counting and leaves the triage queue. Retracting ne… |
No output schema declared.
No examples provided.
remember_about_person Remember about the person ~357
Remember something stable about THIS person, so the next conversation does not start from zero. Allowed keys, and only these: role, industry, delivery_place, language, price_attitude, doc_requirements. An unknown key is reported back by name and the other facts in the same call are still stored. `source` must say where it came from: `human` if the person stated it, `model` if you inferred it. 🔴 It is not a label: it decides whether the write lands. What the person stated outright overwrites anything; an inference overwrites only another inference. A `model` write onto a trait the person stated themselves comes back with `why: "person_said_it"` and `current` holding what they said — ask them about the discrepancy instead of deciding for them. Within one source the newer value always wins, so a person who changed where they ship stops being remembered with the old place. the person stated it, `model` if you inferred it. `recall` is the one-line outcome of this conversation ("looked for 500 m of cable to Berlin, left no enquiry"). Do NOT send name, email or phone — they are not kept here: a copy that never updates would have the agent writing to a stale address. Do NOT send the product, volume, deadline or spec either — those belong to the enquiry and change every time. The person is taken from the visitor token; a guest gets `sign_in_required`. The answer says per key whether it was stored.
| Name | Type | Req | Description |
|---|---|---|---|
| facts | array | – | Stable traits of the person. Up to six distinct keys. |
| recall | string | – | One line on how this conversation ended. Cut at 300 characters. |
No output schema declared.
No examples provided.
request_quote Request a quote ~370
Send a request for prices, samples or terms to a manufacturer on the person's behalf. Requires the person's own name and email — ask them and pass exactly what they give you, never invent an address. The manufacturer receives the request; the person receives an email with a sign-in link where the reply and the supplier's contacts appear. No account is needed beforehand. Use it once they have chosen a supplier.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Name of the agent or platform sending this, e.g. "Claude" — recorded as the source. |
| buyer_company | string | – | Their company name, if known. |
| buyer_country | string | – | ISO 3166-1 alpha-2 country of the buyer. |
| buyer_email | string | yes | The person's real email — the reply and the sign-in link go there. |
| buyer_name | string | yes | The person's name, as they gave it. |
| locale | string | – | – |
| manufacturer_slug | string | yes | Target manufacturer slug, from search_products or list_manufacturers. |
| message | string | yes | What they need: specs, volumes, target price, delivery terms. |
| operation_id | string | – | Optional idempotency key for this attempt. Retrying with the SAME operation_id returns the original result instead of creating a second RFQ — send one if your transport can retry. No token needed: an… |
| product_id | string | – | Product the request is about, if one was chosen. |
| quantity | integer | – | Desired quantity. |
| variant_key | string | – | Version of that product the person chose, when get_product lists `variants` (e.g. "400v"). Requires product_id. The manufacturer sees the version and its model code in the request. |
No output schema declared.
No examples provided.
search_products Search products ~408
PARTIAL RESULTS: `count` is how many came back, `total` how many match in all. If `has_more` is true you are looking at a slice — raise `limit` (up to 50), page with `offset`, or say you checked the first N of M. Do NOT report that nothing matches based on a partial slice. Search wholesale products published on Gemalli. Narrow by free text, category, manufacturer, country of origin, maximum minimum-order quantity, maximum price or delivery basis (Incoterms 2020 codes the seller confirmed). Returns product cards in the requested language with price range, minimum order and the supplier. Use it when the person is looking for GOODS to buy or source. When the question is about the COMPANIES themselves — who makes something, which factories or producers are on the platform — use list_manufacturers instead: this tool returns goods, and a list of goods is not an answer about companies.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug filter (categories.slug). |
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. "UA"). |
| incoterms | array | – | Delivery basis filter, Incoterms 2020 codes (e.g. ["FCA","DAP"]). A product matches when the seller confirmed ANY of the listed codes. Products without confirmed terms ("Incoterms on request") never… |
| limit | integer | – | Max results (1–50). Defaults to 12. |
| locale | string | – | Preferred locale for returned text. |
| manufacturer | string | – | Manufacturer slug filter (manufacturers.slug). |
| moqMax | integer | – | Max minimum-order-quantity threshold (inclusive). |
| offset | integer | – | Pagination offset. |
| priceMax | number | – | Max `price_from` threshold (inclusive). |
| q | string | – | Free-text search across name + description (FTS via migration 0016 with ILIKE fallback). |
No output schema declared.
No examples provided.
submit_join_request Request to join ~314
Send the platform team a request to join Gemalli — for a manufacturer, trader, sales agent, logistics or customs operator, broker or finance provider who wants to work with the platform rather than buy on it. Requires their name, email and phone: the team follows up by phone, so a number is needed. Ask them and pass exactly what they give you, never invent contact details. Use it only when the person has asked to be contacted, never to record someone you are merely discussing.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_role | string | – | What they do: producer, trader, sales_agent, logistics, broker or finance. |
| company | string | – | Their company, if known. |
| country | string | – | ISO 3166-1 alpha-2 country of the person. |
| string | yes | Their real email. Required. | |
| locale | string | – | Two-letter language the person speaks, for the follow-up. |
| message | string | – | What they are looking for, in their own words where possible. |
| name | string | yes | The person's name, as they gave it. |
| operation_id | string | – | Optional idempotency key. Retrying with the SAME operation_id returns the original lead instead of creating a duplicate. |
| phone | string | yes | Their phone in international format. Required. |
| source | string | – | Where this lead came from, e.g. your agent name — recorded for the sales team. |
| trade_direction | string | – | What they buy or sell, short free text. |
No output schema declared.
No examples provided.
How do I install the Gemalli B2B Trade MCP server?
Gemalli B2B Trade is a hosted endpoint at https://gemalli.com/api/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 · gemalli.com
claude mcp add --transport http com-gemalli-trade 'https://gemalli.com/api/mcp'
What is the Gemalli B2B Trade MCP server?
Gemalli B2B Trade is an MCP server listed in the public MCP registry as com.gemalli/trade. Global B2B trade: verified manufacturers, product search, sanctions screening, HS codes. This page covers its hosted endpoint (https://gemalli.com/api/mcp).
Is the Gemalli B2B Trade MCP server safe to use?
Gemalli B2B Trade 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 Gemalli B2B Trade MCP server expose?
Gemalli B2B Trade exposes 28 tools: list_manufacturers, get_manufacturer, search_products, get_product, list_categories, and 23 more. Their descriptions and schemas cost roughly 5,635 tokens of context every time the server is loaded.
Does the Gemalli B2B Trade MCP server require authentication?
No. We connected to Gemalli B2B Trade without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Gemalli B2B Trade MCP server still maintained?
Gemalli B2B Trade 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 Gemalli B2B Trade MCP server?
VerifyMCP ran 13 checks on Gemalli B2B Trade, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.