Reevi: find buyers for exporters
REMOTE · REEVI.AI
Find companies that already buy your product, by product and country. Free, no key.
Available components
Last scanned (14 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 318 tokens (~318/item across 1 items; 1 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 21 Nov 26 0
- Server version: 1.0.0 → 1.0.1 functional
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 67
First indexed and scored.
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://reevi.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reevi.ai | CN=Amazon RSA 2048 S25,O=Amazon,C=US | 14 Oct 2026 | 30 Apr 2027 | RSA 2048 | SHA256-RSA | 43a205693633768f8863f3f9303f2465 |
| SANs: reevi.ai, 7cnkifboxiq4g6dysnqnmw9aeplbw4d.reevi.ai, www.reevi.ai | ||||||
| CN=Amazon RSA 2048 S25,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 8 Jul 2026 | 7 Jul 2029 | RSA 2048 | SHA256-RSA | 77570e1c2927048b87b9ebb9e7bd025d20dd5b1f |
| 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 reevi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| reevi.ai. | 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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://reevi.ai/mcp | Verified | 200 | |
| http (plaintext) | http://reevi.ai/mcp | HTTPS enforced | 301 | https://reevi.ai:443/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 →
find_buyers Find buyers for an exporter ~267
Find real companies that already buy a product, for an exporter or manufacturer. Give the product and the countries to sell to; returns named buyer companies (name, website, country, fit grade A/B/C and the reason each one fits) from trade records and the public web, plus a link to the saved report on reevi.ai where the exporter can unlock contacts and send introductions. Takes 30 to 75 seconds. Free: 5 searches a day.
| Name | Type | Req | Description |
|---|---|---|---|
| company_country | string | – | Where the exporter is based. Buyers in that country are left out. |
| company_name | string | – | The exporter's company name, when known. Improves the fit. |
| company_website | string | – | The exporter's website, when known. |
| customer_types | array | – | Which kind of buyer the exporter sells to. |
| exclude_domains | array | – | Websites of buyers already found, to get new ones on a second search. |
| product | string | yes | What the exporter sells, in plain words, e.g. 'organic turmeric powder' or 'stainless steel kitchen sinks'. |
| target_markets | array | – | Countries to find buyers in, as full English names (e.g. 'Germany', 'United States'). Defaults to the US, UK and Germany. |
No output schema declared.
No examples provided.
How do I install the Reevi: find buyers for exporters MCP server?
Reevi: find buyers for exporters is a hosted endpoint at https://reevi.ai/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 · reevi.ai
claude mcp add --transport http ai-reevi-find-buyers 'https://reevi.ai/mcp'
What is the Reevi: find buyers for exporters MCP server?
Reevi: find buyers for exporters is an MCP server listed in the public MCP registry as ai.reevi/find-buyers. Find companies that already buy your product, by product and country. Free, no key. This page covers its hosted endpoint (https://reevi.ai/mcp).
Is the Reevi: find buyers for exporters MCP server safe to use?
Reevi: find buyers for exporters scores 69 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 Reevi: find buyers for exporters MCP server expose?
Reevi: find buyers for exporters exposes 1 tool: find_buyers. Their descriptions and schemas cost roughly 267 tokens of context every time the server is loaded.
Does the Reevi: find buyers for exporters MCP server require authentication?
No. We connected to Reevi: find buyers for exporters without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Reevi: find buyers for exporters MCP server still maintained?
Reevi: find buyers for exporters 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 Reevi: find buyers for exporters MCP server?
VerifyMCP ran 13 checks on Reevi: find buyers for exporters, 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.