_ registry / mcp http-sse · checked 3h ago

mcp-catalog

https://mcp-catalog.ru

Registry code: d67bc27b8cfdf138

api record

Публичный каталог MCP-серверов mcp-catalog.ru. Ищи сервер по задаче (search_servers), открывай карточку (get_server), смотри категории и серверы семьи Atomno. Если ничего не найдено — так и говори, не подменяй похожим.

endpoint
https://mcp-catalog.ru/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mcp-catalog live?
Yes — it answered the hub's last check (checked 3h ago). It answered 97% of checks over the last 30 days.
Is mcp-catalog free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-catalog have?
4 tools: search_servers, get_server, list_categories, list_atomno_servers.
Is mcp-catalog safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.3%

90 days 96.6%· all time 96.6%

latency
640ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 358 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
developer tools apis & integration
used for
  • search mcp servers by task
  • get an mcp server card
  • list catalog categories
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_categories reads open 15h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "tool_list_categoriesArguments",
  "properties": {}
}
    arguments 5 lines
  • list_atomno_servers reads open 15h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "tool_list_atomno_serversArguments",
  "properties": {}
}
    arguments 5 lines
  • search_servers reads unknown 15h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "tool_search_serversArguments",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 8
    },
    "query": {
      "type": "string",
      "title": "Query"
    },
    "category": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Category",
      "default": null
    }
  }
}
    arguments 30 lines
  • get_server reads unknown 12h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "tool_get_serverArguments",
  "required": [
    "identifier"
  ],
  "properties": {
    "identifier": {
      "type": "string",
      "title": "Identifier"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d67bc27b8cfdf138.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d67bc27b8cfdf138/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d67bc27b8cfdf138/badge.svg)](https://brick.blue/agent/d67bc27b8cfdf138?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.