Vargov®Design
REMOTE · VARGOV.RU
Read-only MCP server with Vargov®Design public data: compositions, answers, configurator, dealers.
Available components
Last scanned (10 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 969 tokens (~193/item across 5 items; 5 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 Management10
- Stability observed for 3 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 72
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 5 Nov 2026 · Probed https://vargov.ru/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vargov.ru | CN=YE1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6688e74293da7f1afd0aeab323ca9fc2445 |
| SANs: vargov.ru, www.vargov.ru | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vargov.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | DS published | 26734 | 8 | Verified |
| vargov.ru. | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://mc.yandex.ru https://cdn.jsdelivr.net; worker-src 'self' blob:; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://mc.yandex.ru https://*.3ddd.ru https://b6.3ddd.ru https://i.ytimg.com; font-src 'self' data:; connect-src 'self' blob: https://mc.yandex.ru https://mc.yandex.com wss://mc.yandex.ru wss://mc.yandex.com https://cdn.jsdelivr.net https://huggingface.co https://*.hf.co https://cdn-lfs.hf.co https://cdn-lfs-us-1.hf.co; frame-src 'self' https://configurator.vargov.ru https://vargov.design https://www.youtube.com https://youtube.com https://rutube.ru https://*.rutube.ru https://mc.yandex.ru; media-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vargov.ru/api/mcp | Verified | 200 | |
| http (plaintext) | http://vargov.ru/api/mcp | HTTPS enforced | 301 | https://vargov.ru/api/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 →
ask_brand Verified brand answers ~183
Published answers of Vargov®Design about ordering, production time, delivery, installation, certification, warranty, the configurator, BIM/IFC, colours and finishes, with the pages they come from. Answers are matched by the words of the question, not by meaning: up to three candidates, best word match first, each to be quoted as written only if it actually answers the question. found=false only when the question shares too few words with the published answers; when no answer fits, use the contact links for a manager. Works best with the question in English or Russian; lang sets the answer language (English where no translation exists).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the result: ru, en, de, it, fr, es, vi or ar. Default en. |
| question | string | yes | The question, preferably in English or Russian. |
No output schema declared.
No examples provided.
configurator_link Configurator link with dimensions ~171
A link that opens the Vargov®Design 3D configurator with the zone dimensions already filled in: length, width and, optionally, the height of the element cloud, in millimetres. With an LC code the configurator opens with that composition; compositions it does not build to room dimensions open without them (calculation: individual or not_by_room_size).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Optional LC article code. |
| height_mm | integer | – | Height of the element cloud, mm (optional). |
| lang | string | – | Language of the result: ru, en, de, it, fr, es, vi or ar. Default en. |
| length_mm | integer | yes | Length of the zone, mm. |
| width_mm | integer | yes | Width of the zone, mm. |
No output schema declared.
No examples provided.
dealers_and_showroom Dealers and showroom ~77
Official Vargov®Design dealers with their regions and contacts, the brand's showroom in Moscow (address, daily hours, phone, map links) and the brand's direct contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the result: ru, en, de, it, fr, es, vi or ar. Default en. |
No output schema declared.
No examples provided.
get_composition Composition facts ~172
Facts about one composition by its LC code, as its page on vargov.ru shows them: description, where it works, style, elements in stock, the serial certificate (regulations and validity; the document numbers are on the composition page), the free 3D model (max, fbx), videos and awards — plus the element material where the brand has confirmed it. A null field means the brand does not state it, not that the answer is no. No prices: every composition is made to order and the price is calculated for each project.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | LC article code: LC0413, lc 413 or 413. |
| lang | string | – | Language of the result: ru, en, de, it, fr, es, vi or ar. Default en. |
No output schema declared.
No examples provided.
search_compositions Find compositions ~236
Find Vargov®Design compositions by the image or shape of their elements — butterflies, stingrays, birds, droplets, leaves, spheres, rings, spirals and more, in any of the site's eight languages — and/or by product type. Returns LC codes with page links and cover images, best matches first; the brand's own examples come first. For the facts about one composition call get_composition.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | lighting_composition — the catalogue type “Lighting composition” (almost all of them hang from the ceiling); sconce — wall lamps; mirror — mirrors; panel — wall compositions; floor_lamp — the floor a… |
| lang | string | – | Language of the result: ru, en, de, it, fr, es, vi or ar. Default en. |
| limit | integer | – | How many to return, 1–20. Default 10. |
| motif | string | – | Image or shape of the elements in any site language: butterflies, бабочки, Schmetterling, stingrays, droplets, spheres… |
No output schema declared.
No examples provided.
How do I install the Vargov®Design MCP server?
Vargov®Design is a hosted endpoint at https://vargov.ru/api/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 · vargov.ru
claude mcp add --transport http ru-vargov-vargov-design 'https://vargov.ru/api/mcp'
What is the Vargov®Design MCP server?
Vargov®Design is an MCP server listed in the public MCP registry as ru.vargov/vargov-design. Read-only MCP server with Vargov®Design public data: compositions, answers, configurator, dealers. This page covers its hosted endpoint (https://vargov.ru/api/mcp).
Is the Vargov®Design MCP server safe to use?
Vargov®Design scores 73 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 Vargov®Design MCP server expose?
Vargov®Design exposes 5 tools: search_compositions, get_composition, ask_brand, configurator_link, dealers_and_showroom. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.
Does the Vargov®Design MCP server require authentication?
No. We connected to Vargov®Design without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vargov®Design MCP server still maintained?
Vargov®Design 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 Vargov®Design MCP server?
VerifyMCP ran 13 checks on Vargov®Design, 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.