ru.meetslava/hr
REMOTE · MEETSLAVA.RU
HR-инструменты: поиск кандидатов, оценка match, интервью, управление рекрутментом.
Available components
Last scanned (53 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 20 Aug 2026.
Category CRM and Sales
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 27 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Aug 26 −16
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 24 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.40 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 20 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 27 Aug 2026 · Probed https://meetslava.ru/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of meetslava.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| meetslava.ru. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meetslava.ru/mcp | Unreachable | ||
| http (plaintext) | http://meetslava.ru/mcp | HTTPS enforced |
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_about_experience ~117
Точечный вопрос про опыт кандидата: «работал ли с X?», «что делал в Y?». Сервер отдаёт релевантные данные — вывод формирует ассистент. / Ask a specific question about the candidate's background.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| question | string | yes | Вопрос рекрутёра, до 1000 символов |
No output schema declared.
No examples provided.
assessment ~211
Тестовое задание кандидату. action=send — отправить (нужны title, body, recruiterContact; кандидат загрузит решение файлом); action=status — статус и ссылка на скачивание решения (нужен assessmentId). / Send a take-home assessment or check its status and download link.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Действие: send | status |
| assessmentId | integer|null | – | assessmentId из ответа send (status) |
| body | string|null | – | Текст задания, до 5000 символов (send) |
| candidate | string|null | – | Slug кандидата. В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| deadlineIso | string|null | – | Опц. дедлайн в ISO-8601 UTC (send) |
| recruiterContact | string|null | – | Контакт рекрутёра для вопросов (send) |
| title | string|null | – | Короткое название задания, до 200 символов (send) |
No output schema declared.
No examples provided.
get_conditions ~125
На каких условиях кандидат готов выйти: зарплатные ожидания (base, бонус, equity, deal-breakers), срок выхода, формат работы, гео/таймзона, виза, релокация. lang: ru (по умолчанию) или en. / Candidate's terms: compensation expectations, notice period, work format, location, visa.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата. В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| lang | string|null | – | Язык: ru или en |
No output schema declared.
No examples provided.
get_contacts ~84
Прямые контакты кандидата (телефон, email, мессенджеры). Выдаются после того, как вы представились через recruiter_context. / Direct contacts; introduce yourself via recruiter_context first.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
No output schema declared.
No examples provided.
get_faq ~88
Ответы кандидата на типовые вопросы рекрутёров — проверьте здесь, прежде чем писать ему. / Candidate's answers to common recruiter questions.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| lang | string|null | – | Язык: ru или en |
No output schema declared.
No examples provided.
get_profile ~119
Визитка кандидата: имя, город, краткое описание + ссылки (GitHub, LinkedIn, сайт, образцы работ). Начните знакомство отсюда. lang: ru (по умолчанию) или en. / Candidate overview: name, city, summary, GitHub/LinkedIn/website links.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата. В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| lang | string|null | – | Язык: ru или en |
No output schema declared.
No examples provided.
get_references ~79
Рекомендации о кандидате от бывших коллег и руководителей (с их согласия) — trust-сигнал перед офером. / References from former colleagues and managers.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
No output schema declared.
No examples provided.
get_resume ~116
Полное резюме кандидата: опыт по местам работы, достижения, навыки. Начните отсюда, если нужна полная картина. / Full resume: work history, achievements, skills.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| resumeId | integer|null | – | ID резюме (из list_resumes). Если не указано — возвращается primary резюме кандидата. |
No output schema declared.
No examples provided.
manage_interview ~360
Назначить кандидату интервью и управлять им. action=propose — предложить слоты (нужны companyName, proposedSlots ISO-8601 UTC, channel, interviewType, recruiterContact); action=reschedule — заменить слоты (нужны conversationId, proposedSlots); action=cancel — отозвать приглашение (нужен conversationId). / Propose, reschedule or cancel an interview with the candidate.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Действие: propose | reschedule | cancel |
| candidate | string|null | – | Slug кандидата. В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| channel | string|null | – | Канал связи: Zoom, Google Meet, Phone, ... (propose) |
| companyName | string|null | – | Название компании (propose) |
| conversationId | integer|null | – | conversationId треда интервью из message_candidate (reschedule/cancel) |
| durationMinutes | integer|null | – | Длительность в минутах (propose/reschedule, опц.) |
| interviewType | string|null | – | Тип интервью: intro, technical, cultural, final (propose) |
| notes | string|null | – | Заметки: что обсуждаем, кто на звонке (propose, опц.) |
| proposedSlots | array|null | – | 1-5 слотов в ISO-8601 UTC, напр. ['2026-07-17T15:00:00Z'] (propose/reschedule) |
| reason | string|null | – | Причина отмены (cancel, опц.) |
| recruiterContact | string|null | – | Контакт рекрутёра для подтверждения (propose) |
No output schema declared.
No examples provided.
match_vacancy ~130
Вставьте текст описания вакансии — получите структурированную оценку соответствия: совпавшие навыки, сеньорность, условия выхода. / Paste a job description to evaluate candidate fit.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| lang | string|null | – | Язык публичных секций: ru (по умолчанию) или en |
| vacancyText | string | yes | Текст описания вакансии, до 5000 символов |
No output schema declared.
No examples provided.
message_candidate ~220
Переписка с кандидатом. Без параметров text/conversationId — список тредов; с conversationId — история треда; с text — отправить сообщение (кандидат отвечает в мессенджере). / Messaging: list threads, read a thread, or send a message.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| conversationId | integer|null | – | Id существующего треда, чтобы дописать в него или прочитать историю |
| recruiterContact | string|null | – | Контакт рекрутёра для ответа (обязателен при открытии нового треда) |
| subject | string|null | – | Тема треда (обязательно при открытии нового треда), до 200 символов |
| text | string|null | – | Текст сообщения, до 3000 символов. Не указан — режим чтения (треды/история) |
No output schema declared.
No examples provided.
recruiter_context ~161
Представьтесь: компания, имя, роль. Кандидат увидит, кто им интересуется, а вам откроются контакты (get_contacts). Укажите email, под которым вошли. / Introduce yourself to unlock contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| company | string|null | – | Компания |
| string | yes | Email рекрутёра (ключ лида) | |
| name | string|null | – | Имя рекрутёра |
| notes | string|null | – | Заметки: что ищете, контекст |
| role | string|null | – | Роль/должность |
No output schema declared.
No examples provided.
send_vacancy ~276
Отправить кандидату вакансию — первый шаг, если он вам подходит. В личном режиме кандидат один: параметр candidate указывать НЕ нужно. recruiterContact тоже можно не указывать — подставится ваш email из авторизации. Кандидат получит уведомление и сможет ответить. / Send a vacancy; candidate and recruiterContact are optional here.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string|null | – | Slug кандидата (из search_candidates). В личном режиме не обязательно: отправьте null или не передавайте параметр. |
| company | string | yes | Название компании (для инлайн-отправки; при vacancyId игнорируется) |
| recruiterContact | string|null | – | Контакт рекрутёра для ответа. Можно не указывать — возьмётся ваш email из авторизации. |
| resumeId | integer|null | – | ID резюме кандидата (из list_resumes). Если не указано — используется primary резюме. |
| vacancyId | integer|null | – | id сохранённой вакансии (из list_vacancies). Указан — берётся она + HR-профиль, инлайн-текст игнорируется |
| vacancyText | string | yes | Описание вакансии до 3000 символов (для инлайн; при vacancyId игнорируется) |
No output schema declared.
No examples provided.
How do I install the ru.meetslava/hr MCP server?
ru.meetslava/hr is a hosted endpoint at https://meetslava.ru/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 · meetslava.ru
claude mcp add --transport http ru-meetslava-hr 'https://meetslava.ru/mcp'
What is the ru.meetslava/hr MCP server?
ru.meetslava/hr is an MCP server listed in the public MCP registry as ru.meetslava/hr. HR-инструменты: поиск кандидатов, оценка match, интервью, управление рекрутментом. This page covers its hosted endpoint (https://meetslava.ru/mcp).
Is the ru.meetslava/hr MCP server safe to use?
ru.meetslava/hr scores 0 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 ru.meetslava/hr MCP server expose?
ru.meetslava/hr exposes 13 tools: recruiter_context, get_contacts, ask_about_experience, message_candidate, send_vacancy, and 8 more. Their descriptions and schemas cost roughly 2,086 tokens of context every time the server is loaded.
Does the ru.meetslava/hr MCP server require authentication?
Its publisher declares no required credentials for ru.meetslava/hr. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ru.meetslava/hr MCP server still maintained?
ru.meetslava/hr has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 20 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.