Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

mcp-catalog

REMOTE · MCP-CATALOG.RU

Search MCP servers in the public mcp-catalog.ru directory.

Available components

0 this week 79 Trust /100

Last scanned (10 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 311 tokens (~77/item across 4 items; 4 tools + 0 resources), lean.Pass
  • 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 Coverage71
  • 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
  • Structured output schemas are declared (100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 3 Nov 26 0
    • DNSSEC: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 2 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 1 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 0
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
  • 20 Sept 26 0
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
  • 2 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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://mcp-catalog.ru/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp-catalog.ru CN=YE2,O=Let's Encrypt,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA384 6464dd688e83417b42638ba090297018efe
SANs: mcp-catalog.ru
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 mcp-catalog.ru. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ru. present 26734 8 Verified
mcp-catalog.ru. absent 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=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp-catalog.ru/mcp Verified 200
http (plaintext) http://mcp-catalog.ru/mcp HTTPS enforced 308 https://mcp-catalog.ru/mcp
MCP tools · 4 exposed · ~245 tokens

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 →

Tool Tokens
get_server ~71

Карточка одного сервера из каталога: описание, ссылка на страницу, репозиторий, пакет. Идентификатор — короткий slug, адрес /servers/автор/название, имя или имя пакета. Если карточки нет — found=false.

NameTypeReqDescription
identifierstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_atomno_servers ~55

Публичные MCP-серверы семьи Atomno из этого каталога (ЕГРЮЛ, ФНС, ФССП, курсы ЦБ и др.). Только то, что уже есть на сайте.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_categories ~27

Список категорий каталога и сколько в каждой серверов. Только публичные данные сайта.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

search_servers ~92

Найти MCP-сервер в каталоге mcp-catalog.ru по формулировке задачи (например: «ЕГРЮЛ», «postgres», «курсы ЦБ»). Возвращает только реальные совпадения. Если ничего не нашлось — found=false, без подмены похожими.

NameTypeReqDescription
category–––
limitinteger––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the mcp-catalog server?

mcp-catalog is a hosted endpoint at https://mcp-catalog.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 · mcp-catalog.ru

# add to Claude Code
claude mcp add --transport http atomno-mcp-mcp-catalog 'https://mcp-catalog.ru/mcp'
Common questions

What is the mcp-catalog server?

mcp-catalog is listed in the public MCP registry as io.github.atomno-mcp/mcp-catalog. Search MCP servers in the public mcp-catalog.ru directory. This page covers its hosted endpoint (https://mcp-catalog.ru/mcp).

Is the mcp-catalog server safe to use?

mcp-catalog scores 79 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 mcp-catalog server expose?

mcp-catalog exposes 4 tools: search_servers, get_server, list_categories, list_atomno_servers. Their descriptions and schemas cost roughly 245 tokens of context every time the server is loaded.

Does the mcp-catalog server require authentication?

No. We connected to mcp-catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the mcp-catalog server still maintained?

mcp-catalog 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.