Cuevr
REMOTE · WWW.CUEVR.COM
Read-only tools: search the site, read pages, see plans, price a quote, cite sourced figures.
Available components
Last scanned (16 hours ago)
Scores higher than 88% 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 Security80
- 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
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2512 tokens (~193/item across 13 items; 13 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 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
- Structured output schemas are declared (23% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Nov 26 0
- Stability: 0.97 → pass security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 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.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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://www.cuevr.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cuevr.com | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 88cfadc866687652134f2a1b07485039 |
| SANs: cuevr.com, www.cuevr.com, *.www.cuevr.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.cuevr.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| cuevr.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=15552000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'self' |
| 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://www.cuevr.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.cuevr.com/mcp | HTTPS enforced | 301 | https://www.cuevr.com/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 →
atouts What the product does best ~171
Lists the product's published capabilities with their promise and proof page, the problems it solves, what the plan includes and the published comparison pages, ranked by the need given. Use it when the buyer must choose or asks why this product: what does it do best, is it right for our need. To compare with a named tool, use comparer; for one feature, chercher; for prices, voir_offres. Facts about this product only: about other tools, only what the comparison pages publish.
| Name | Type | Req | Description |
|---|---|---|---|
| besoin | string | – | The buyer's need or criteria, in their words (e.g. read tracking, tenders). Ranks the capabilities. |
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
No output schema declared.
No examples provided.
calculer_roi Estimate the return on investment ~279
Runs the ROI calculator published on the site, with exactly its formulas and bounds. Use it when the buyer asks what the product would bring them: deals won, revenue, time saved. Call it without values to get its inputs (label, bounds, default), ask the buyer for their own figures, then pass x1, x2… Returns each result with its calculation, the inputs used, the published assumptions and the page to quote. For a price, use devis; for a published statistic, citer_chiffre.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| x1 | number | – | Proposals sent per month, whole team (proposals): 1 to 200, default 10. |
| x2 | number | – | Current close rate (%): 0 to 100, default 20. |
| x3 | number | – | Average signed deal value (€ excl. VAT): 0 to 1000000, step 5000, default 10000. |
| x4 | number | – | Close rate increase (points): 0 to 50, default 10. |
| x5 | number | – | Number of sales reps (sales reps): 1 to 50, default 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| avertissement | string | – | – |
| calculateur | string | – | – |
| consigne | string | – | What to do with the result. |
| entrees | array | – | – |
| erreur | string | – | Why the call was refused and what to fix. |
| hypotheses | array | – | – |
| langue | string | yes | Language of the answer. |
| resultats | array | – | – |
| url | string | – | Page of the calculator, to quote. |
No examples provided.
chercher Search the site ~187
Searches the site's pages and returns the passages that answer, each with its URL and section anchor, and a confidence. Use it for facts about the product: can it do X, a feature, integrations, security, GDPR, a sector. Steps in the app: comment_faire; prices: voir_offres or devis; comparison: comparer. Returns excerpts: read the page with lire_page before stating a detail they lack. Confidence moyenne or faible: first say what the site does not cover, then give the closest page.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| limite | integer | – | Maximum number of passages (1 to 10, default 5). |
| requete | string | yes | The buyer's question or its key words, in the language of the answer. |
No output schema declared.
No examples provided.
citer_chiffre Quote a sourced figure ~163
Returns the figures published on the site (statistics, results, market data) with their value, label, source URL, date and the page that publishes them. Use it before quoting any figure that is not a price. Quote the figure exactly as returned, with its source and date; never round or extrapolate it. For prices use voir_offres or devis; for an estimate for the buyer, calculer_roi. Returns only published figures: when none matches, give no figure.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| requete | string | – | Words to look for in the figure or its label. Without it, all figures. |
| Name | Type | Req | Description |
|---|---|---|---|
| chiffres | array | – | – |
| consigne | string | – | What to do with the result. |
| erreur | string | – | Why the call was refused and what to fix. |
| langue | string | yes | Language of the answer. |
No examples provided.
comment_faire How to do it in the product ~172
Returns the steps from the user documentation for a task in the app, with the app labels as written and the URL of the section to quote. Use it when the buyer asks how to do something in the product: how do I invite a colleague, where do I see why a prospect declined, how do I export a PDF, how do I create an API key. To know whether the product can do something, or what a feature brings, use chercher. Covers the documentation only: no prices, no comparisons.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| question | string | yes | What the person wants to do, in their words (e.g. share a proposal with a decision-maker). |
No output schema declared.
No examples provided.
comparer Compare with another tool ~183
Returns the passages of the published comparison pages that answer, each with its page to quote, and the tools a page covers. Use it when the buyer compares this product with another tool or a kind of tool: Cuevr or PandaDoc, an alternative to Word, Cuevr or an e-signature tool. To know if it works with a tool already in use (keep Docusign, an integration): chercher; without a named tool: atouts. A tool no page covers is listed in nonCouverts: say nothing about it.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| question | string | yes | The buyer's comparison in their words, with the tools named (e.g. Cuevr or PandaDoc for a team of 10). |
No output schema declared.
No examples provided.
conseils Sales advice ~218
Returns selling advice published on the site (follow-ups, proposal structure, qualification, pricing, negotiation, tenders), each with its page to quote. Use it for a method question that does not depend on the product: how many follow-ups without being pushy, what goes in a proposal, how to qualify a deal. When the buyer describes their own problem and asks how the product helps, use resoudre_probleme; for a product fact, chercher. Returns advice only, no product features or prices.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| requete | string | – | Words to look for in the advice. |
| secteur | string | – | Sector of the buyer, when known (agences, conseil, esn, saas). |
| sujet | string | – | Topic: closing, relances (follow-ups), structure, qualification, prix (pricing), negociation, appels-offres (tenders), cycle. |
No output schema declared.
No examples provided.
demander_demo Prepare a demo request link ~202
Returns a link to the demo request form, prefilled with the details given. Use it outside the browser when the buyer wants a demo or to talk to the team. Opening the link shows the filled form: the person, or their browser agent, sends it, then the person picks and confirms the time slot in the calendar. Sends nothing by itself. To try the product alone, use demarrer_essai.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Work email address of the person. Personal mailboxes (Gmail, Outlook, Yahoo…) are refused. | |
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| nom | string | – | Last name of the person. |
| prenom | string | – | First name of the person. |
| societe | string | – | Company of the person. |
| telephone | string | – | Phone number of the person (optional). |
No output schema declared.
No examples provided.
demarrer_essai Start a free trial ~99
Returns the sign-up link of the free trial and its conditions. Use it when the buyer wants to start a trial now. Whether a trial exists and its conditions, together with prices, come from voir_offres. Creates no account: the person signs up and accepts the terms.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
No output schema declared.
No examples provided.
devis Price a quote ~208
Prices a number of users (1 or more) from the published prices: unit price, total per period and per year, yearly saving, the calculation and the pricing page. Use it for any total: a team, several users, or one user over a year, even as an example; call it as soon as a team size or period is known. Never compute a total yourself. Unit prices and plans: voir_offres.
| Name | Type | Req | Description |
|---|---|---|---|
| facturation | string | – | Billing: mensuel (monthly) or annuel (yearly). Without it, both. |
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| plan | string | – | Key or name of the plan, as returned by voir_offres. Without it, every plan. |
| sieges | integer | yes | Number of users (seats) to price, as the buyer gave it. Ask for it rather than assume one. |
| Name | Type | Req | Description |
|---|---|---|---|
| consigne | string | – | What to do with the result. |
| erreur | string | – | Why the call was refused and what to fix. |
| langue | string | yes | Language of the answer. |
| plans | array | – | – |
| sieges | integer | – | Number of users priced. |
| source | object | – | – |
No examples provided.
lire_page Read a page ~189
Returns the text of one page of the site, or of one section by its anchor, with its exact URL. Use it before stating a detail that is not in an excerpt returned by another tool: a condition, a limit, a legal point, how a feature works. Give a URL returned by a tool; with its #anchor, only that section is returned, which is shorter. Reads only pages of this site: to find a page, use chercher.
| Name | Type | Req | Description |
|---|---|---|---|
| ancre | string | – | Anchor of one section of the page (without #): returns that section only. |
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| url | string | yes | URL or path of a page of this site, as returned by a tool. With a #anchor, only that section is returned. |
No output schema declared.
No examples provided.
resoudre_probleme Solve a sales problem ~192
Diagnoses a sales problem of the buyer's team: likely causes, what the product does for each with the page proving it, and the pages to quote (sector page first). Use it when the buyer describes their problem or asks how the product would help their company: we lose to cheaper rivals, clients haggle over our fees, prospects go silent. Pass secteur when known. For selling advice without the product, use conseils. Returns summaries: read a page with lire_page for details.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
| secteur | string | – | Sector of the buyer, when known (agences, conseil, esn, saas). |
| symptome | string | yes | The problem in the buyer's words (e.g. our prospects stop replying after the proposal). |
No output schema declared.
No examples provided.
voir_offres See plans and prices ~142
Returns the plans, the price per user (amount, currency, period, taxes), what each plan includes, the free trial and its conditions, and the trial and demo links, as the pricing page publishes them. Use it for: how much per user, is yearly billing cheaper, is there a free trial, is a card needed, what is included. For any total (a team, several users, one user over a year), call devis: never multiply a price yourself. Returns no total.
| Name | Type | Req | Description |
|---|---|---|---|
| langue | string | yes | Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language. |
No output schema declared.
No examples provided.
How do I install the Cuevr MCP server?
Cuevr is a hosted endpoint at https://www.cuevr.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 · www.cuevr.com
claude mcp add --transport http com-cuevr-mcp 'https://www.cuevr.com/mcp'
What is the Cuevr MCP server?
Cuevr is an MCP server listed in the public MCP registry as com.cuevr/mcp. Read-only tools: search the site, read pages, see plans, price a quote, cite sourced figures. This page covers its hosted endpoint (https://www.cuevr.com/mcp).
Is the Cuevr MCP server safe to use?
Cuevr scores 86 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 Cuevr MCP server expose?
Cuevr exposes 13 tools: chercher, lire_page, resoudre_probleme, conseils, calculer_roi, and 8 more. Their descriptions and schemas cost roughly 2,405 tokens of context every time the server is loaded.
Does the Cuevr MCP server require authentication?
No. We connected to Cuevr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cuevr MCP server still maintained?
Cuevr 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 Cuevr MCP server?
VerifyMCP ran 13 checks on Cuevr, 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.