Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Reevol Source: supplier search

REMOTE · SOURCE.REEVOL.COM

Search and compare 200,000+ global suppliers by brief, name, HS code or country. Free, no key.

0 this week 85 Trust /100

Last scanned (16 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3119 tokens (~183/item across 17 items; 14 tools + 3 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 Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% 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
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Server version: 1.7.0 → 1.7.1 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 0
    • Tool “request_supplier_listing” rewrote its description, which is the text the model reads security
  • 10 Nov 26 +1

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

  • 9 Nov 26 0
    • Tool “find_suppliers_by_country” rewrote its description, which is the text the model reads security
    • Tool “find_suppliers_by_hs_code” rewrote its description, which is the text the model reads security
    • Tool “get_similar_suppliers” rewrote its description, which is the text the model reads security
    • Tool “get_supplier” rewrote its description, which is the text the model reads security
    • Tool “match_suppliers_by_brief” rewrote its description, which is the text the model reads security
    • Tool “search_suppliers” rewrote its description, which is the text the model reads security
    • Schema quality: 163 → 183 ▼ functional
    • Server version: 1.6.0 → 1.7.0 functional
  • 8 Nov 26 +1

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

  • 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 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://source.reevol.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=source.reevol.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 17 Sept 2026 2 Apr 2027 RSA 2048 SHA256-RSA 6ea793a61f892f9ef204cfc1a1e54ee
SANs: source.reevol.com, www.source.reevol.com, aeo5sxvvkybgsmy74cse782qnwb2psd.source.reevol.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of source.reevol.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
reevol.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://source.reevol.com/mcp Verified 200
http (plaintext) http://source.reevol.com/mcp HTTPS enforced 301 https://source.reevol.com:443/mcp
MCP tools · 14 exposed · ~2,681 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_suppliers ~108

Side-by-side comparison of 2-4 suppliers by slug: identity, location, certifications, trade-fair count, employee range, year founded, HS code overlap, and visibility. Read-only, no key required. Returns shared signals (common HS codes / certifications / country) so you can summarize the trade-offs for a buyer.

NameTypeReqDescription
langstring–Locale for the returned URLs. Default en.
slugsarrayyes2-4 supplier slugs to compare.

No output schema declared.

No examples provided.

draft_rfq ~104

Generate a professional RFQ (request for quotation) email body grounded in the supplier's facts and the buyer's brief. Returns the draft text only; nothing is sent. Chinese-region suppliers get a bilingual EN+zh draft. Requires a partner or enterprise key.

NameTypeReqDescription
briefstringyesWhat the buyer wants to source.
buyerCompanystring––
quantitystring–Target order size / quantity, free text.
slugstringyes–

No output schema declared.

No examples provided.

find_and_brief ~224

One-shot deep research. Runs the full pipeline in a single call: shortlist (semantic + structured match), a structural dossier with due-diligence signals per supplier, an AI-synthesized comparison grounded strictly in that data, and a recommended next step. Returns the complete result (non-streaming) — use this when your agent cannot consume the /mcp/deep SSE stream. Results are cached for 24h on identical brief + filters, so repeated calls are cheap and citations are stable. Requires a partner or enterprise key.

NameTypeReqDescription
briefstringyesFreeform description of what the buyer is sourcing.
businessTypestring––
certificationsarray––
countriesarray––
countrystring––
employeeRangearray––
excludeCountriesarray––
exportMarketsarray––
foundedAfterinteger––
foundedBeforeinteger––
hsCodesarray––
industrystring––
langstring––

No output schema declared.

No examples provided.

find_suppliers_by_country ~244

List suppliers headquartered in a given country, optionally filtered by industry, certifications, employee range, or business type. Every result matches the filters equally, so the list is ordered by visibility score. Ranking: by relevance first. Among about equally relevant results, suppliers on a paid Reevol plan come first and carry featured: true, and catalog completeness counts for a little. Payment never lifts a supplier above a clearly better match or removes anyone from results.

NameTypeReqDescription
businessTypestring–Restrict to manufacturer vs trading company.
certificationsarray–Certification names to require (any-of). E.g. ["ISO 9001","BSCI"].
countrystringyesCanonical country name, e.g. "China", "Vietnam", "Turkey".
employeeRangearray–Employee bands to allow. E.g. ["1-10","11-50","51-200","201-500","500+"].
industrystring–Primary industry filter (matches Reevol industry taxonomy).
langstring–Locale for the returned URLs. Default en.
limitinteger–Max results, default 10.

No output schema declared.

No examples provided.

find_suppliers_by_hs_code ~273

List suppliers that manufacture or trade goods under a given Harmonized System code, with optional structured filters. Use this when a buyer asks 'find me a supplier for HS code 8473.30' or 'who makes [HS-described product]'. Ranking: by relevance first. Among about equally relevant results, suppliers on a paid Reevol plan come first and carry featured: true, and catalog completeness counts for a little. Payment never lifts a supplier above a clearly better match or removes anyone from results.

NameTypeReqDescription
businessTypestring–Restrict to manufacturer vs trading company.
certificationsarray–Certification names to require (any-of). E.g. ["ISO 9001","BSCI"].
countrystring–Canonical country name (e.g. "China", "Vietnam"). Optional.
employeeRangearray–Employee bands to allow. E.g. ["1-10","11-50","51-200","201-500","500+"].
hsCodestringyesFull or partial HS code (2-12 digits). E.g. "8473.30" or "847330".
langstring–Locale for the returned URLs. Default en.
limitinteger–Max results, default 10.

No output schema declared.

No examples provided.

get_red_flags ~72

Structured due-diligence scan for one supplier: missing data, certification freshness, trade-fair recency, data completeness, and enrichment staleness. Structural signals only, never an accusation or credit judgment. Requires a partner or enterprise key.

NameTypeReqDescription
langstring––
slugstringyes–

No output schema declared.

No examples provided.

get_similar_suppliers ~141

Given one supplier slug, return up to 10 similar suppliers in the same industry and country. Use to answer 'what are alternatives to X?' or 'who else makes similar products in [country]?'. Ranking: by relevance first. Among about equally relevant results, suppliers on a paid Reevol plan come first and carry featured: true, and catalog completeness counts for a little. Payment never lifts a supplier above a clearly better match or removes anyone from results.

NameTypeReqDescription
langstring–Locale for the returned URLs. Default en.
limitinteger–Max results, default 10.
slugstringyesReference supplier slug.

No output schema declared.

No examples provided.

get_supplier ~230

Fetch a full supplier profile by slug: identity, location, HS codes, certifications, trade fairs, export markets, and the AI-generated buyer-facing summary + FAQ. Use after search_suppliers to dig into a specific match. When the supplier publishes a Reevol Catalog, a `catalog` block adds its products, certificates, key facts and catalog URL (plus the catalog's own MCP endpoint), and the supplier can be contacted directly with request_introduction, no key needed. When Reevol has verified the company is a real trading business, `catalog.reevolVerified` lists the checks and states what they do and do not assert; when that key is absent it says nothing about the supplier. `featured: true` means the supplier is on a paid Reevol plan, which affects only its position among about equally relevant results.

NameTypeReqDescription
langstring–Locale for the summary + FAQ (en, zh-CN, es, pt-BR, fr, ar). Default en.
slugstringyesSupplier slug, e.g. "shenzhen-acme-electronics-co-ltd".

No output schema declared.

No examples provided.

match_suppliers_by_brief ~370

Best tool when a buyer describes what they need in their own words. Combines semantic search (Voyage embeddings over supplier industry, HS codes, certifications, trade-fair history, and the EN summary) with structured filters (country, HS codes, certifications, employee range, year founded, business type, export markets). Returns a ranked list of supplier cards, each with a `matchExplanation` summarizing why it surfaced. Example brief: 'BSCI-certified Vietnam factory for women's woven outerwear, MOQ-flexible, 11-50 staff, exports to EU'. Ranking: by relevance first. Among about equally relevant results, suppliers on a paid Reevol plan come first and carry featured: true, and catalog completeness counts for a little. Payment never lifts a supplier above a clearly better match or removes anyone from results.

NameTypeReqDescription
briefstringyesFreeform description of what the buyer is sourcing.
businessTypestring––
certificationsarray–Any-of certification names. E.g. ["ISO 9001","BSCI","GOTS"].
countriesarray–Multi-country allow-list. Takes precedence over `country`.
countrystring–Single canonical country name.
employeeRangearray–Allowed employee bands.
excludeCountriesarray–Country deny-list.
exportMarketsarray–Any-of canonical export-market names.
foundedAfterinteger–Minimum year founded.
foundedBeforeinteger–Maximum year founded.
hsCodesarray–Any-of HS codes (2-12 digits each).
industrystring–Primary industry filter.
langstring–Locale for the returned URLs. Default en.
limitinteger–Max results, default 10.

No output schema declared.

No examples provided.

request_introduction ~181

Submit a buyer's interest in a specific supplier. If get_supplier returned a `catalog` block, the supplier takes inbound buyers directly: the request lands in the supplier's own inbox on Reevol and they reply by email. That path is open to every agent, no key needed; pass the buyer's real name and email and a specific brief (products, quantities, destination). For other suppliers it creates a lead that Reevol routes (verified suppliers get a direct intro, unclaimed ones go through Reevol managed sourcing), and that path requires a partner or enterprise key.

NameTypeReqDescription
briefSnippetstringyesWhat the buyer wants to source / why they want the intro.
buyerCompanystring––
buyerEmailstringyesBuyer contact email for the introduction.
buyerNamestring––
slugstringyes–

No output schema declared.

No examples provided.

request_supplier_listing ~415

For agents acting on behalf of a supplier (manufacturer or trading company) that is not on Reevol Source yet. Submits a request to be added; search_suppliers first to make sure the company is not already listed. A 6-digit code is emailed to `email`: read it from that inbox and call verify_supplier_listing. Use the company's own website. A company email is best; an AI-agent mailbox you control (for example *@mail.grokbot.com or *@agentmail.to) is fine as long as the website is the company's own. Free webmail (gmail, qq.com, 163.com, outlook, ...) is not accepted. After verification Reevol reviews the request (an automated check of the website and products, and a person when needed); when the page is live the email gets a "you are live" message with the link, and the supplier manages the profile in Reevi (https://reevi.ai).

NameTypeReqDescription
companyNamestringyesCompany legal or trading name.
contactNamestring–Name of the person at the supplier.
countrystring–Country of the company, e.g. "China".
emailstringyesWhere the 6-digit code is sent. Company email, or an AI-agent mailbox you can read.
hsCodes––HS codes, e.g. ["6802", "6810.99"] or "6802, 6810". Up to 10.
localestring–Language for the emails to the supplier: en, zh-CN, zh-Hant, ja, ko, vi, th, id, es, pt-BR, fr, de, ar. Default en.
mainProductsstring–Main products, plain text.
notestring–Anything the reviewer should know, e.g. "Submitted by an AI agent for the export manager".
websitestringyesThe company's own website, e.g. "minjistone.com".

No output schema declared.

No examples provided.

resend_supplier_listing_code ~50

Email a fresh 6-digit code for a request that is still waiting for verification. Limited to a few sends per request.

NameTypeReqDescription
requestIdstringyesrequestId returned by request_supplier_listing.

No output schema declared.

No examples provided.

search_suppliers ~172

Find suppliers by company name (English or Chinese), brand, or alias. Returns ranked supplier cards. Use this when a buyer mentions a supplier by name or asks 'who is X?'. An exact company-name or website match always comes first. Ranking: by relevance first. Among about equally relevant results, suppliers on a paid Reevol plan come first and carry featured: true, and catalog completeness counts for a little. Payment never lifts a supplier above a clearly better match or removes anyone from results.

NameTypeReqDescription
langstring–Locale for the returned URLs (en, zh-CN, es, pt-BR, fr, ar). Default en.
limitinteger–Max results, default 10.
querystringyesCompany name, brand, or alias. Min 2 chars.

No output schema declared.

No examples provided.

verify_supplier_listing ~97

Second step of request_supplier_listing: pass the requestId it returned and the 6-digit code from the email. Codes expire after 15 minutes and lock after 5 wrong tries (call resend_supplier_listing_code for a new one). On success the request enters the Reevol review queue.

NameTypeReqDescription
codestringyesThe 6-digit code from the email.
requestIdstringyesrequestId returned by request_supplier_listing.

No output schema declared.

No examples provided.

Install

How do I install the Reevol Source: supplier search MCP server?

Reevol Source: supplier search is a hosted endpoint at https://source.reevol.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · source.reevol.com

# add to Claude Code
claude mcp add --transport http com-reevol-source-supplier-search 'https://source.reevol.com/mcp'
Common questions

What is the Reevol Source: supplier search MCP server?

Reevol Source: supplier search is an MCP server listed in the public MCP registry as com.reevol.source/supplier-search. Search and compare 200,000+ global suppliers by brief, name, HS code or country. Free, no key. This page covers its hosted endpoint (https://source.reevol.com/mcp).

Is the Reevol Source: supplier search MCP server safe to use?

Reevol Source: supplier search scores 85 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 Reevol Source: supplier search MCP server expose?

Reevol Source: supplier search exposes 14 tools: search_suppliers, find_suppliers_by_hs_code, find_suppliers_by_country, match_suppliers_by_brief, get_supplier, and 9 more. Their descriptions and schemas cost roughly 2,681 tokens of context every time the server is loaded.

Does the Reevol Source: supplier search MCP server require authentication?

No. We connected to Reevol Source: supplier search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Reevol Source: supplier search MCP server still maintained?

Reevol Source: supplier search 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 Reevol Source: supplier search MCP server?

VerifyMCP ran 13 checks on Reevol Source: supplier search, 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.