_ registry / mcp streamable-http · checked 8h ago

digital.rdk/mcp

https://api.rdk.digital

Registry code: ec8dcaf6ce7e6b54

api record

РДК (Рейтинги digital-компаний, rdk.digital) — каталог кейсов и рейтинги российских digital-агентств. Порядок: find_cases по задаче заказчика → agency_card для понравившихся агентств → prepare_request со списком слагов. Заявку отправляет человек по ссылке request_url: сам вписывает контакты и даёт согласие на ПДн. Контакты пользователя в инструменты не передавайте. Ссылайтесь на url из ответов.

endpoint
https://api.rdk.digital/mcp?ch=registry
protocol
streamable-http ·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 digital.rdk/mcp live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is digital.rdk/mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does digital.rdk/mcp have?
4 tools: find_cases, agency_card, prepare_request, rating.
Is digital.rdk/mcp 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
100%

90 days 100%· all time 100%

latency
402ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ 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
1 open 3 never probed 1 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.

  • rating open 8h ago

    Топ-N опубликованного рейтинга РДК (Рейтинги digital-компаний, rdk.digital) по срезу со ссылкой на страницу и методологию. Без среза — список срезов: homepage (общий), prod (веб-студии), design, mobile, developers, brand, integrators, outstaff, seo, smm, performance.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "top": {
          "type": "integer",
          "maximum": 30,
          "minimum": 1,
          "description": "Сколько мест, по умолчанию 10"
        },
        "slice": {
          "type": "string",
          "description": "Срез: prod, design, mobile, developers, brand, integrators, outstaff, seo, smm, performance, homepage"
        }
      }
    }
    arguments 15 lines
  • find_cases unknown 8h ago

    Подбирает 3–5 реальных кейсов российских digital-агентств под задачу заказчика из каталога РДК (Рейтинги digital-компаний, rdk.digital): название, агентство, год, клиент, результат, награды, ссылка и «почему подходит». С бюджетом — у агентства «цена от» по услуге и пометка budget_fit (кейсы не отсеиваются). Возвращает также request_url — ссылку на подбор с этой задачей, где человек отправляет заявку агентствам.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "Город агентства, если важен"
        },
        "task": {
          "type": "string",
          "description": "Задача своими словами, 10–1000 знаков: что сделать, для какого бизнеса"
        },
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 3,
          "description": "Сколько кейсов, 3–5 (по умолчанию 5)"
        },
        "budget": {
          "type": "string",
          "description": "Бюджет, если назван: «до 2 млн», «от 500 тыс», «1–2 млн». Не фильтр: сверяется с «цена от» агентства"
        },
        "service": {
          "type": "string",
          "description": "Услуга, если названа: «сайт», «мобильное приложение», «SEO»"
        }
      }
    }
    arguments 30 lines
  • agency_card unknown 8h ago

    Справка для решения об агентстве из каталога РДК (Рейтинги digital-компаний, rdk.digital): места в рейтингах РДК и лучшее место, кейсы по годам и услугам, награды, клиенты, город, сайт, цены «от», места во внешних рейтингах со ссылкой на источник.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Слаг агентства — из ответа find_cases/rating или адреса rdk.digital/agency/<slug>"
        }
      }
    }
    arguments 12 lines
  • prepare_request unknown 35h ago

    Готовит черновик заявки агентствам из каталога РДК (Рейтинги digital-компаний) и ссылку rdk.digital/podbor с задачей и выбранными агентствами. Заявку отправляет человек на сайте: сам вписывает контакты и ставит согласие на обработку ПДн. Контакты через этот инструмент не передаются.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task"
      ],
      "properties": {
        "task": {
          "type": "string",
          "description": "Задача, 10–1000 знаков"
        },
        "agencies": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "description": "Слаги агентств (из find_cases/agency_card/rating)"
        }
      }
    }
    arguments 20 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 ec8dcaf6ce7e6b54.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ec8dcaf6ce7e6b54/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/ec8dcaf6ce7e6b54/badge.svg)](https://brick.blue/agent/ec8dcaf6ce7e6b54?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.