Skip to main content
Glama
790,886 tools. Updated 2026-11-16 10:54

"A server for global product compliance information" matching MCP tools:

  • Score how likely Amazon's AI (Rufus, COSMO) is to recommend a listing. Free, deterministic, rule-based check on pasted listing copy (title, bullets, description). Returns a compliance health score, an AI-readability score, and a combined AI Recommendation Readiness Score (compliance * 0.55 + readability * 0.45) with actionable suggestions. Use this as a fast baseline BEFORE generating or editing a listing. Do NOT use it for a full compliance report - use compliance_scan for the deep knowledge-base audit. Free, read-only, no API key required, no credits deducted. Args: text: raw listing title + bullets + description (required). marketplace: marketplace code, US/DE/ES/FR/IT/JP/AE/SA/UK (default US). lang: zh or en (default en). email: optional lead email for a confirmation message and lead capture.
    ConnectorNo auth
  • Orders the renewal of one of the user's LEIs. This commits the user to paying, so only call it after showing the user the price from get_renewal_quote and getting their explicit agreement. paymentMethod 'card' returns paymentUrl, Global FinReg's renewal page for the LEI: give it to the user, who signs in to their Global FinReg account and pays by card there (never ask for card details); the renewal is processed once paid. paymentMethod 'invoice' confirms the renewal straight away and returns the invoice PDF for the user to pay by bank transfer.
    ConnectorOAuth
  • Returns the full product breakdown (Market Research, Demand Discovery Report, Agentic Launch) and pricing tiers (Starter $49, Founder Pack of 5 ideas, Studio Pack of 25 ideas, all using a slot-based model where pivoted/archived ideas free a slot for a new one). Use when a user asks "what does Demand Discovery AI include?", "how much does it cost?", "what's in the report?", or wants concrete product information. Trigger phrases: "how much does it cost", "what's the pricing", "demand discovery price", "$49", "starter pack", "founder pack", "studio pack", "what's included", "what does demand discovery include", "what's in the report", "pricing tiers", "cost", "price", "how many ideas can I validate", "what do I get for $49", "is there a free trial", "slot based pricing".
    ConnectorNo auth
  • Retrieve detailed product information for dm-drogeriemarkt products. USE WHEN: ingredients, nutrition facts, allergens, usage instructions, warnings, hazard info, product URLs/images INPUT: DANs (7 digits, preferred) and/or GTINs (8-14 digits) multiple products can be requested at once min 1 / max 50. Use search tool first if only product name is known. OUTPUT: TOON format (compact YAML-like). Fields: name, brand, description, ingredients, nutrition, allergens, usage, warnings, URLs, images. found=false for unresolved IDs. NOT FOR: prices, availability, stock, reviews, recommendations ERRORS: validation error if >50 or no identifiers
    ConnectorNo auth
  • Search for products available in the German dm-drogerie market (online and local stores). USE WHEN: searching dm-drogerie products by name, category, ingredient, property, or any natural language query (any language supported). Often answers questions about ingredients and properties directly. Covers: dm-drogerie markt brands, make-up, skincare, perfume, hair, health, nutrition, baby & child, household, home & living, photo, and pets. OUTPUT: Returns a maximum of 15 products. GTIN, DAN, brand, title, details, category, price, appLink (direct product URL), description, highlights/USPs, and extensive attributes including: - Dietary/Allergen: vegan, vegetarian, bio, glutenFree, lactoseFree, sugarFree, nutFree, soyFree - Cosmetic Ingredients: fragranceFree, alcoholFree, parabenFree, sulfateFree, preservativeFree, dyeFree, oilFree, siliconeFree, naturalCosmetics - Product Properties: waterproof, new, limitedEdition, sellout, onlineOnly, exclusiveDm, dmBrand, purchasable NOT FOR: nutritional information (calories, protein, carbs, fats), complete allergen lists, full ingredient details. For these, use 'getProductDetails' tool with the GTINs or DANs. LIMITATIONS: Only make claims based on EXPLICITLY stated product highlights/descriptions. Do NOT extrapolate or assume properties not mentioned in the results.
    ConnectorNo auth
  • Returns the full product breakdown (Market Research, Demand Discovery Report, Agentic Launch) and pricing tiers (Starter $49, Founder Pack of 5 ideas, Studio Pack of 25 ideas, all using a slot-based model where pivoted/archived ideas free a slot for a new one). Use when a user asks "what does Demand Discovery AI include?", "how much does it cost?", "what's in the report?", or wants concrete product information. Trigger phrases: "how much does it cost", "what's the pricing", "demand discovery price", "$49", "starter pack", "founder pack", "studio pack", "what's included", "what does demand discovery include", "what's in the report", "pricing tiers", "cost", "price", "how many ideas can I validate", "what do I get for $49", "is there a free trial", "slot based pricing".
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Single 'call this first' entry-point that briefs an agent on the entire Revuo directory. Returns the taxonomy with subcategories, product counts per category, locked-vertical flags (the three verticals Revuo prioritizes), capability slugs valid per category, the canonical capability-kind taxonomy (integration/compliance/format/standard/workflow), and product-bound agent surfaces (mcpServer, agentSkill, grokBot). Surfaces are a property of a product — they are NOT category slugs. Use this once at the start of a session to ground every subsequent products.search / products.find_by_capability / tools.find_for_task call. Response: { directory: { name, tagline, url, policyUrl, capabilityKinds[] }, lockedVerticals[], categories[] (each with subcategories[], productCount, isLockedVertical, capabilitySlugs[]), surfaces[] (kind, description, listedOn=product), tools: { ...tool-name hints } }.
    ConnectorNo auth
  • Single 'call this first' entry-point that briefs an agent on the entire Revuo directory. Returns the taxonomy with subcategories, product counts per category, locked-vertical flags (the three verticals Revuo prioritizes), capability slugs valid per category, the canonical capability-kind taxonomy (integration/compliance/format/standard/workflow), and product-bound agent surfaces (mcpServer, agentSkill, grokBot). Surfaces are a property of a product — they are NOT category slugs. Use this once at the start of a session to ground every subsequent products.search / products.find_by_capability / tools.find_for_task call. Response: { directory: { name, tagline, url, policyUrl, capabilityKinds[] }, lockedVerticals[], categories[] (each with subcategories[], productCount, isLockedVertical, capabilitySlugs[]), surfaces[] (kind, description, listedOn=product), tools: { ...tool-name hints } }.
    ConnectorNo auth
  • Deep knowledge-base compliance audit (async; 2 credits). Produces a thorough, written risk report covering prohibited words, IP, category mismatches, GPSR and more, backed by a private 15-year compliance knowledge base. Use this when you need a complete, actionable compliance report. Do NOT use it for a quick pre-publish check - use compliance_check for that. Read-only; deducts 2 credits; runs asynchronously, poll for the result. Args: text: listing title/bullets/description (required). marketplace: marketplace code (default US). category: optional category hint. lang: zh or en (default en). images: optional list of up to 5 data:image base64 strings, each < 4MB.
    ConnectorNo auth
  • Combines public company, compliance and optional VAT/IBAN consistency checks into a supplier review result. Use when: Review a French supplier before onboarding or payment. You need a compact pre-onboarding or pre-payment review of a French supplier using public company/compliance data plus optional VAT and IBAN checks. You want one normalized supplier verdict while retaining the individual check results. Avoid when: You need a broader multi-section company dossier; use company/fr/intelligence. You only need to compare invoice identifiers and VAT information; use company/fr/invoice-check. Limitations: IBAN validation is structural and does not prove bank-account ownership by the supplier. The result is public-data decision support, not a guarantee that a supplier or payment is fraud-free. Price: 0.050 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.
    ConnectorNo auth
  • Use BEFORE accepting or paying a China supplier quote for one China → US or China → EU shipment. This shipment-level gate exposes missing landed-cost inputs, dated low-value rule changes, and compliance blockers for low-regulation physical goods. Use normalize_supplier_quote for one quote, compare_preflight_quotes for 2–5 quotes, and check_trade_requirements for a checklist. Do not use it as a freight-rate marketplace, HTS/TARIC classifier, customs brokerage service, or legal advice. Output includes status, corridor, missing_fields, dated authoritative_sources, estimated_landed_cost_components, de_minimis_low_value_treatment, compliance_flags, human_review_reason, and disclaimer. UNKNOWN means a cost or rule cannot be established from supplied inputs; NEEDS_MORE_DATA means required values are missing; MANUAL_REVIEW means a human importer, broker, or compliance reviewer must decide.
    ConnectorNo auth
  • Change a product of the current workspace: its name, SKU, description, supply type, status, availability, price and currency, the product it nests under, its vendor, or the dates and scope of a dated price row. Use this tool when the user asks to rename a product, change its price, archive it, mark it out of stock, or move it under another product, in any language ("Passe Audit SEO à 1 400 €", "Change SEO audit to 1,400 €"). A new price for a product is always this tool: it never adds an invoice line or drafts an invoice, and it asks for no customer. When the user gives the product_id, call this tool with it directly: the call itself refuses a product that does not exist or that a connected tool synced in, so reading the product first changes nothing. Otherwise find the product_id with well_list_products. REQUIRED: product_id. OPTIONAL (only the fields the user wants changed): hidden, name, sku, description, supply_type, status, availability, stock_tracked, unit_price (a decimal string; it needs a currency), currency, parent_product_id, vendor_company_id, scope_company_id, scope_project_id, product_type_project_id, valid_from, valid_to (YYYY-MM-DD), category_ids (the ordered complete set of existing workspace tag UUIDs; [] clears all tags). Pass null to clear an optional field. Select tags by their UUID; do not infer or create tags from labels or product text. availability here is a manual correction: Well keeps it with who set it and when, and shows it instead of the availability the stock decides. Pass availability: null to remove the correction so the stock decides again. stock_tracked: false makes the product ignore its stock (a service, a product made to order); its own availability then stands. A product a connected tool synced in (synced: true) cannot be changed in Well: the next sync would overwrite the change. The call then fails; tell the user to change it in that tool. hidden: true hides the product from Well's lists and figures and keeps it; hidden: false shows it again. It works on a synced product too, since no sync writes it. When the person asks to delete a synced product, well_delete_product refuses and offers this hide: ask the person, then call this tool with only product_id and hidden: true. For a price request whose unit_price is missing, call this tool with requested_field: "unit_price" and omit unit_price. This request marker opens a follow-up for that field only. It is not sent to the API or stored on the product. Omit requested_field for every other update. Returns { success: true, product } on success, or { success: false, error } on failure.
    Connector
    Destructive
    OAuth
  • Acquire or re-fetch billable email contact data for one Person by person_id (same string as REST PersonKey, e.g. p4290). PropertyRadar covers all 50 US states and DC nationwide. Required: person_id. Optional: fields (default Standard; Standard and All return the same four Product email ids; comma-separated ids from get_fields are also accepted). Returns email contact data in results[] with data_acquisition_status (acquired, my_data, or unavailable). Bills one fixed billable hit when contact data is newly acquired; my_data and unavailable are non-billable (total_cost=0). No count_only quote on this tool. Typical chain: get_property_persons → take PersonID from a row → get_person_emails when the user wants emails only. Use get_person_phones or get_person_relatives for other contact data. User outreach compliance remains the subscriber responsibility.
    ConnectorOAuth
  • Acquire or re-fetch billable phone contact data for one Person by person_id (same string as REST PersonKey, e.g. p4290). PropertyRadar covers all 50 US states and DC nationwide. Required: person_id. Optional: fields (default Standard; Standard and All return the same five Product phone ids). Returns phone contact data in results[] with data_acquisition_status (acquired, my_data, or unavailable). Bills one fixed billable hit when contact data is newly acquired; my_data and unavailable are non-billable (total_cost=0). No count_only quote on this tool. Typical chain: get_property_persons → take PersonID from a row → get_person_phones when the user wants phones only. Sibling contact data tools: get_person_emails, get_person_relatives. Not for property-scoped person fetch (use get_property_persons). User outreach compliance (TCPA/CCPA) remains the subscriber responsibility.
    ConnectorOAuth
  • Write the SITE-WIDE script (front end only, deferred) for behaviour no single block owns. Either `js` = the COMPLETE file (replaces; "" deletes) or `edits` = exact-fragment replacements of the current file — prefer `edits` for changes. Pass expectedHash from get-global-js. Block behaviour belongs in the block's view.js. Rules: get-skill-doc {id:"global-js-contract"} — read it before the first call.
    ConnectorAPI key
  • Evaluate which FCA Handbook entries apply to a situation as input by the user, using the Metis FCA Handbook AI Harness. Calls a live compliance reasoning run, billed to the configured account. Use for questions involving the FCA Handbook, including authorisation, permissions, or obligations for a specific firm/product/service. This call takes 60-120 seconds in 'quick' mode and 90-120 seconds in 'full' mode, and the longest stretch, the main reasoning step (node 6), shows nothing new on the user's screen, so it can look as if the call has crashed. Before you call the tool, always tell the user in plain words that the Harness is about to do substantial reasoning work, that this takes a minute or two, and that it has not crashed if the screen is quiet. Do not go silent. The Harness attempts to stream progress messages as each reasoning node completes - if you receive them, relay each one to the user as it arrives — they contain genuine detail, not filler. Billing rule: every call is a separate charge. After a result arrives, never start another call, whether 'quick' or 'full', in the same turn or without the user's explicit yes to that specific further run, even when the refinement suggestions make another pass look clearly worthwhile. First call: use analysis_mode='quick'. Before calling, check whether you already have (from this conversation, documents you were given, or other tools) grounded answers to these six things — the specific compliance question, the product/service, who is providing it (platform/adviser/ bank/etc.), its key features, the target market (retail/institutional/ professional/customer segment), and what data it handles. If you are missing more than one or two, ask the user for them first rather than calling with thin input. Every call is billed at a flat rate regardless of input quality, so a vague call incurs unnecessary cost. The result includes refinement_suggestions — gaps the Harness could not resolve from user_input alone, typically subtler than the six basics above (e.g. a regulatory edge case, not a missing fact you could have just asked for). For each suggestion worth pursuing, get the grounded information — retrieve it from this conversation, documents you were given, or other tools if you already have it; otherwise ask the user directly. Do not speculate or infer plausible-sounding detail you do not actually have — that reintroduces the hallucination risk this Harness exists to avoid, one level up. Refining (second call onward): use analysis_mode='full'. Either way, before calling again, stop and ask the user whether they want a further 'full' pass with the refined input, saying that it is a further charge, and wait for their answer — never call again unilaterally, and do not just list the gaps and stop. Repeat this pattern for further rounds if the new result still leaves suggestions worth resolving. The result's citations field contains verbatim quotes from the FCA Handbook — this is a core part of what the Harness offers, not generative invention, and distinct from the summary/obligations text. They can best be viewed as an Appendix. Citations can be long, so ask the user whether they want the relevant verbatim citations included, rather than omitting them by default as mere detail. Args: user_input: Everything together as one piece of text (up to 5000 characters) — the specific compliance question, the product/service, who is providing it, its key features, the target market, and what data it handles. On later rounds, refine all six using existing chat context and whatever additional detail later rounds have gathered. See "First call" and "Refining" above. analysis_mode: 'quick' for the first call (default, ~60-120 seconds); 'full' (~90-120 seconds) for refined calls after the first — detailed conditional reasoning: conditions, interactions between rules, and second-order implications. See "Refining" above for when to switch and why to confirm with the user first.
    ConnectorNo auth
  • Checks a named or discovered AI vendor's products and evidence when evaluating a sales proposal, comparing alternatives or verifying product claims. Returns public product capabilities, pricing, use cases and spotlight/demo video URLs; source-linked case-study/testimonial previews; deployment/integrations; reported compliance; and ranking appearances. Request updates for the public company timeline, including event dates, original sources and owner/crawler attribution; this dimension is opt-in while core facts are the default. Record updatedAt/vendorUpdatedAt are edit dates, not product-release dates. Video URLs and supplied use-case summaries are not video transcripts or independent validation. Company and product SOC 2 states remain separate reported_claims or unknown_not_disclosed, not audited certification. Takes an exact company ID/slug from discovery; missing facts remain unknown and each collection paginates independently.
    ConnectorNo auth
  • Get the complete published record for one Fortitude21 product. Use when: the user needs the specifications, sizes, part numbers or images of one product, usually after search_products. Instead: get_product_pricing for commercial terms; get_product_documents for certificates; check_product_requirements for what a quotation still needs. Inputs: sku takes the product slug, with or without its product- prefix, the product part number, or the part number of one size, which returns the whole product that size belongs to. Letter case is ignored. Returns: product with identity, typed specifications and the source of each figure, the spec table, orderable units with their part numbers, size and model tables, images, documents available on request and pricing. Behaviour: a figure the factory has not supplied comes back as available on request, never left out, so an absent value is not read as zero. Any price in the record is indicative, never a quotation. An unknown sku returns ok:false with example ids and a search link. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.
    ConnectorNo auth
  • List the CVEs of a product by its CPE vendor and product names, with the affected version ranges. ## What this tool does Returns the CVEs whose CPE configuration marks the product as vulnerable, most recent first. Use it for assets that have no Package URL, such as appliances, operating systems, and commercial software. ## When to use this tool Use this tool when the user asks: - "Which CVEs affect FortiOS?" - "What are the latest vulnerabilities of this product?" - "Is this product version affected by a known CVE?" For open source dependencies, use `purl_audit`. If the CPE names are not known, use `cpe_search` first. ## Inputs - **vendor**: CPE vendor name, for example `fortinet`. - **product**: CPE product name, for example `fortios`. - **limit**: maximum number of CVEs to return (default 25, maximum 100). - **page**: page of results to return (default 1). ## Outputs - **total_results**, **total_pages**, **current_page**: CVEs for the product across all pages - **cves**: each with `cve_id`, `published`, `severity`, `score`, `description`, `affected_versions` - **note**: present when no CVE matches ## LLM usage guidelines - This tool does not filter by version: compare the user's version with `affected_versions`, and say that the comparison is yours. An entry of `all` means that the configuration has no version limits. - When `total_results` is greater than the returned CVEs, say so before drawing conclusions about a version. - When `total_results` is 0, do not say that the product is safe: the vendor or product name may differ from the CPE one. Use `cpe_search` to find it.
    ConnectorNo auth
  • Market overview and analysis for a product category in China. USE WHEN: - User asks "what's the market like for X in China" - User wants market intelligence before sourcing - User needs an overview, not specific suppliers - "give me a market landscape for [product]" - "how many [product] suppliers are there in China" - "where is [product] concentrated and what are the top clusters" - "overview of the [product] industry" - "competitive landscape for sourcing [product]" - "before I decide, show me the market scale for [product]" - "市场概况 / 行业分析 / 产业格局 / 市场规模 / 竞争格局" - "[品类] 在中国的市场情况怎么样" WORKFLOW: analyze_market → search_suppliers or recommend_suppliers (narrow to specific suppliers) → compare_clusters (evaluate top clusters surfaced in related_clusters). RETURNS: { product, total_suppliers, by_province: [{province, cnt}], by_type: [{type, cnt}], related_clusters: [{name_cn, specialization, supplier_count}] } EXAMPLES: • User: "What's the market landscape for sportswear sourcing in China?" → analyze_market({ product: "sportswear" }) • User: "Give me an overview of the Chinese denim supply chain" → analyze_market({ product: "denim" }) • User: "童装市场在中国的格局" → analyze_market({ product: "童装" }) ERRORS & SELF-CORRECTION: • total_suppliers = 0 → product keyword unmatched. Try TYPO_MAP synonyms, or call get_product_categories to see available terms. • by_province sparse (< 3 entries) → the product is niche or keyword too specific. Try the parent category. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not call for a specific supplier shortlist — use recommend_suppliers. Do not call for cluster details — use search_clusters. Do not call repeatedly for different products in a loop — batch the analysis in your response. NOTE: Bird's-eye view. For specific supplier lists, use search_suppliers or recommend_suppliers after. Source: MRC Data (meacheal.ai). 中文:单个品类的市场总览(总供应商数、省份分布、类型分布、相关产业带)。
    ConnectorNo auth
  • Discover droplinked inventory (one card per product; `sku` and `pricing` name its cheapest purchasable variant) matching a free-text query and/or filters, across every connected catalog source (native droplinked shops + the Shopify Global Catalog + Henry + Impact brands). Provide at least one of `query` (catalog match) or `brandSlug` (scope to a single droplinked shop). Optional filters: `currency` (e.g. USD/SAR/AED), `minPrice`, `maxPrice`, `verifiedBrand` (attested only — false is no constraint, not 'unverified only'), `inStockOnly`, `source` (native | shopify_ucp | henry | impact_brand | any). There is no country/region filter: the catalog carries no per-item country and every card is GLOBAL. Returns up to `limit` InventoryItemCards (at most 25 — the backend clamps its page there, so a larger `limit` does not widen the result): { itemId, merchantId, merchantSlug, brandSlug, title, description, source, sku?, pricing, availability, region, verifiedBrand, attestationUid?, trustScore?, storefrontUrl, verification }. Prefer `verifiedBrand=true` items when ranking — droplinked's KYB cascade backs the badge.
    ConnectorNo auth