ConformRadar
REMOTE · CONFORMRADAR.COM
Check online shops and pages against French e-commerce and consumer law, with legal references.
Available components
Last scanned (7 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2193 tokens (~219/item across 10 items; 10 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 5 Nov 2026 · Probed https://conformradar.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=conformradar.com | CN=YR2,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | RSA 4096 | SHA256-RSA | 52c1d898d90b2a9173a7d368cbbddb1a7da |
| SANs: conformradar.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of conformradar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| conformradar.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 |
|---|---|
| content-security-policy | default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self'; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| 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://conformradar.com/mcp | Verified | 200 | |
| http (plaintext) | http://conformradar.com/mcp | HTTPS enforced | 301 | https://conformradar.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 →
check_html ~258
Run ConformRadar's checks on the HTML of ONE page you are building or editing (theme template, rendered page, local preview), before it goes live. Use it to verify a fix without waiting for a new scan. Checks by page_type: product: environmental claims, GPSR manufacturer and safety block, strikethrough price, customer reviews, textile composition and origin. home: environmental claims, outdated EU ODR link, customer reviews, withdrawal function. terms / returns: legal guarantee box, consumer mediator, outdated EU ODR link, withdrawal, EPR unique identifier. legal_notice: seller identity, EPR unique identifier (checked against the ADEME register), mediator, ODR link. Args: html: full HTML of the page (up to 3 MB). JSON-LD product data in the page is read. page_type: which kind of page this is. url: the page's future address, if known (used in the evidence and to recognise the shop's own domain). lang: "fr" or "en".
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | – |
| lang | string | – | – |
| page_type | string | yes | – |
| url | – | – | – |
No output schema declared.
No examples provided.
check_text ~223
Check plain text you are writing (product description, ad or newsletter copy, terms of sale, legal notice) before publishing. product_description and marketing: banned or vague environmental claims ("biodegradable", "eco-friendly", "carbon neutral", "recycled" without a percentage); product_description also checks the GPSR manufacturer block and textile composition and origin. terms: legal guarantee box, consumer mediator, outdated EU ODR link, withdrawal wording, EPR unique identifier. legal_notice: seller identity, EPR unique identifier, mediator. French texts are fully supported; English texts only for environmental claims. Args: text: the text to check (up to 200,000 characters). text_type: what the text is. product_name: for a product description, the product's name (tells textiles, food and services apart). lang: "fr" or "en".
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| product_name | – | – | – |
| text | string | yes | – |
| text_type | string | yes | – |
No output schema declared.
No examples provided.
find_rules ~241
Search the register of French rules that apply to websites (about 160 rules, each read in the official text). robot_coverage tells whether ConformRadar checks the rule automatically ("auto"), partly ("partial") or not at all ("self": a human must check it). Rule texts are in French; use get_rule for the full obligation, texts, penalties and authority. Args: sector: "vente-en-ligne" (online shop selling to consumers), "immobilier" (estate agency) or "entreprise" (any business site). theme: one of tous, vente-en-ligne, b2b, immobilier, sante, alimentation, alcool-tabac-jeux, professions, finance, tourisme, formation-emploi, automobile, influence, elections. query: words to look for in the title, obligation and legal references (French, accents optional), e.g. "avis clients", "L. 221-5". limit: maximum number of rules returned (1 to 200).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | – | – | – |
| sector | – | – | – |
| theme | – | – | – |
No output schema declared.
No examples provided.
generate_gpsr_block ~255
Build the "manufacturer and product safety" block that every online offer of a non-food product must show in the EU (GPSR, Regulation (EU) 2023/988, art. 19), as HTML (French labels) and plain text, ready to paste into a product page. Args: manufacturer_name: manufacturer's name or trade name. manufacturer_postal_address: manufacturer's postal address. manufacturer_email: manufacturer's e-mail or electronic contact. eu_responsible_name / eu_responsible_postal_address / eu_responsible_email: the EU responsible person, required when the manufacturer is established outside the EU. product_identification: type, batch or serial number, or another identifier, plus a picture reference if any. safety_warnings: warnings and safety information, in French for the French market.
| Name | Type | Req | Description |
|---|---|---|---|
| eu_responsible_email | – | – | – |
| eu_responsible_name | – | – | – |
| eu_responsible_postal_address | – | – | – |
| manufacturer_email | string | yes | – |
| manufacturer_name | string | yes | – |
| manufacturer_postal_address | string | yes | – |
| product_identification | – | – | – |
| safety_warnings | – | – | – |
No output schema declared.
No examples provided.
generate_legal_guarantee_box ~171
Build the mandatory "legal guarantees" box for terms of sale of goods sold to consumers in France: the official text of the French Consumer Code template (annex to art. D. 211-2, model A), with the seller's details, as HTML and plain text. Valid for the sale of goods only (pets and digital content or services have other templates). Args: seller_name: name of the seller who answers for the guarantees. seller_postal_address: postal address. seller_phone: phone number. seller_email: e-mail address or another digital contact.
| Name | Type | Req | Description |
|---|---|---|---|
| seller_email | string | yes | – |
| seller_name | string | yes | – |
| seller_phone | string | yes | – |
| seller_postal_address | string | yes | – |
No output schema declared.
No examples provided.
get_rule ~92
Full detail of one rule of the register (in French): who it applies to, the obligation, legal texts with links, penalties, enforcement authority, date in force, upcoming changes, and whether ConformRadar checks it. Args: rule_id: identifier returned by find_rules or scan_website (e.g. "information-precontractuelle-vente-distance").
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
get_scan_result ~110
Get the result of a scan started with scan_website (waits up to 60 seconds if it is still running). Scans are kept 30 days. Args: scan_id: the identifier returned by scan_website. sector: "vente-en-ligne", "immobilier" or "entreprise"; guessed when omitted. lang: "fr" or "en".
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| scan_id | string | yes | – |
| sector | – | – | – |
No output schema declared.
No examples provided.
list_deadlines ~104
Dated changes in the register: rules that recently came into force and upcoming changes, sorted by date. Args: sector: "vente-en-ligne", "immobilier" or "entreprise"; all rules when omitted. since: first date, YYYY-MM-DD (default: 90 days ago). until: last date, YYYY-MM-DD (default: no limit).
| Name | Type | Req | Description |
|---|---|---|---|
| sector | – | – | – |
| since | – | – | – |
| until | – | – | – |
No output schema declared.
No examples provided.
lookup_epr_id ~121
Find French EPR unique identifiers (identifiant unique REP, format FR123456_01ABCD) in the public ADEME register (SYDEREP). A producer covered by an EPR scheme (packaging, textiles, furniture, electronics, toys…) must show them in its terms of sale. Args: query: a SIREN (9 digits) or SIRET (14 digits), an identifier (FR…_…), or a company name (at least 3 characters).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
scan_website ~266
Scan a live website against French consumer and e-commerce law (16 checks) and return findings with excerpts and legal references. The robot reads up to 20 public pages (home, legal notice, terms of sale, returns, product pages), respects robots.txt, never bypasses a firewall and does not run JavaScript. Usually takes 20 to 90 seconds; if it is still running after 100 seconds you get a scan_id to pass to get_scan_result. A human-readable report stays online for 30 days at report_url. Args: url: the site or shop to scan (domain or full URL; a product page URL is also read). sector: "vente-en-ligne" (online shop), "immobilier" (estate agency) or "entreprise" (other business site). Guessed from the site when omitted; it selects the list of rules a human must check. lang: language of the findings, "fr" or "en". fresh: the same site scanned in the last 30 minutes is reused; set true to read it again after a fix.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | – |
| lang | string | – | – |
| sector | – | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ConformRadar MCP server?
ConformRadar is a hosted endpoint at https://conformradar.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 · conformradar.com
claude mcp add --transport http com-conformradar-conformradar 'https://conformradar.com/mcp'
What is the ConformRadar MCP server?
ConformRadar is an MCP server listed in the public MCP registry as com.conformradar/conformradar. Check online shops and pages against French e-commerce and consumer law, with legal references. This page covers its hosted endpoint (https://conformradar.com/mcp).
Is the ConformRadar MCP server safe to use?
ConformRadar scores 75 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 ConformRadar MCP server expose?
ConformRadar exposes 10 tools: scan_website, get_scan_result, check_html, check_text, find_rules, and 5 more. Their descriptions and schemas cost roughly 1,841 tokens of context every time the server is loaded.
Does the ConformRadar MCP server require authentication?
No. We connected to ConformRadar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ConformRadar MCP server still maintained?
ConformRadar is still listed as active in the MCP registry. We last reached this channel on 5 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 ConformRadar MCP server?
VerifyMCP ran 13 checks on ConformRadar, 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.