_ registry / mcp streamable-http · checked 51m ago

xonta-docs

https://mcp.xonta.ru

Registry code: ffcbd9df73abf512

api record

Инструменты для ИИ-агентов, которые готовят российские документы: проверка реквизитов (ИНН, КПП, ОГРН, БИК, счёт, СНИЛС), сумма прописью с НДС, склонение ФИО и должностей по падежам, рабочие дни по производственному календарю РФ. Бесплатно, без регистрации и ключей. Tools for AI agents preparing Russian business documents.

endpoint
https://mcp.xonta.ru/mcp
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 xonta-docs live?
Yes — it answered the hub's last check (checked 51m ago). It answered 100% of checks over the last 30 days.
Is xonta-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does xonta-docs have?
4 tools: amount_in_words, decline_name, validate_requisites, working_days.
Is xonta-docs 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
190ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 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.

  • working_days open 51m ago

    Производственный календарь России с праздниками и переносами. Три режима: (1) date + add_working_days — какая дата будет через N рабочих дней («оплата в течение 5 рабочих дней»); (2) date + end_date — сколько рабочих дней и часов между датами; (3) только date — рабочий ли это день, праздник, сокращённый день и ближайший рабочий день. Russian business-day calendar with official holidays and transfers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "date": {
          "type": [
            "string",
            "number"
          ],
          "description": "Дата ГГГГ-ММ-ДД или ДД.ММ.ГГГГ. По умолчанию сегодня (Москва)"
        },
        "end_date": {
          "type": [
            "string",
            "number"
          ],
          "description": "Конец периода для подсчёта рабочих дней (включительно)"
        },
        "add_working_days": {
          "type": "integer",
          "description": "Сколько рабочих дней прибавить (можно отрицательное)"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • amount_in_words unknown never probed

    Сумма прописью для счетов, актов и договоров: «Одна тысяча двести тридцать четыре рубля 56 копеек». Считает НДС (в том числе или сверху) и выдаёт готовую строку «…, в том числе НДС (22%) 222 руб. 63 коп.». Рубли, доллары, евро, юани. Russian 'amount in words' for invoices with VAT line.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "amount"
      ],
      "properties": {
        "amount": {
          "type": [
            "string",
            "number"
          ],
          "description": "Сумма: 1234.56 или «1 234,56»"
        },
        "kopecks": {
          "enum": [
            "digits",
            "words"
          ],
          "type": "string",
          "description": "Копейки цифрами (по умолчанию) или словами"
        },
        "currency": {
          "enum": [
            "RUB",
            "USD",
            "EUR",
            "CNY"
          ],
          "type": "string",
          "description": "Валюта, по умолчанию RUB"
        },
        "vat_rate": {
          "type": [
            "string",
            "number"
          ],
          "description": "Ставка НДС в процентах (22, 20, 10, 7, 5, 0) или «без НДС». Не указывать — НДС не считается"
        },
        "vat_included": {
          "type": "boolean",
          "description": "true (по умолчанию) — НДС уже в сумме; false — начислить сверху"
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • decline_name unknown 51m ago

    Склоняет ФИО и должность по падежам для договоров, доверенностей и приказов: «в лице генерального директора Иванова Ивана Петровича», «выдана Кузнецовой Анне Сергеевне». Сам определяет пол по отчеству или имени, возвращает полную форму и инициалы. case=all — все шесть падежей сразу. Declines Russian full names and job titles by grammatical case.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "case": {
          "type": [
            "string",
            "number"
          ],
          "description": "Падеж: genitive (родительный, по умолчанию), dative, accusative, instrumental, prepositional, nominative, по-русски, или all"
        },
        "order": {
          "enum": [
            "last_first",
            "first_last"
          ],
          "type": "string",
          "description": "Порядок слов в full_name: last_first (по умолчанию) или first_last"
        },
        "gender": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Пол, если его нельзя определить по отчеству"
        },
        "position": {
          "type": [
            "string",
            "number"
          ],
          "description": "Должность, например «генеральный директор» или «главный бухгалтер»"
        },
        "full_name": {
          "type": [
            "string",
            "number"
          ],
          "description": "ФИО целиком, по умолчанию в порядке «Фамилия Имя Отчество»"
        },
        "last_name": {
          "type": [
            "string",
            "number"
          ],
          "description": "Фамилия (вместо full_name)"
        },
        "first_name": {
          "type": [
            "string",
            "number"
          ],
          "description": "Имя"
        },
        "middle_name": {
          "type": [
            "string",
            "number"
          ],
          "description": "Отчество"
        }
      },
      "additionalProperties": false
    }
    arguments 65 lines
  • validate_requisites unknown 51m ago

    Проверяет российские реквизиты по контрольным суммам: ИНН (10/12 цифр), КПП, ОГРН/ОГРНИП, БИК, расчётный и корреспондентский счёт (ключевание по БИК), СНИЛС. Находит опечатки до выставления счёта или платежа и указывает, если реквизиты похожи на реквизиты разных лиц. Validates Russian company/bank identifiers (INN, KPP, OGRN, BIC, bank account, SNILS) by checksums. Offline, instant.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "bik": {
          "type": [
            "string",
            "number"
          ],
          "description": "БИК банка, 9 цифр. Нужен для проверки счетов"
        },
        "inn": {
          "type": [
            "string",
            "number"
          ],
          "description": "ИНН, 10 или 12 цифр"
        },
        "kpp": {
          "type": [
            "string",
            "number"
          ],
          "description": "КПП, 9 символов"
        },
        "ogrn": {
          "type": [
            "string",
            "number"
          ],
          "description": "ОГРН (13 цифр) или ОГРНИП (15 цифр)"
        },
        "snils": {
          "type": [
            "string",
            "number"
          ],
          "description": "СНИЛС, 11 цифр (можно с дефисами и пробелом)"
        },
        "account": {
          "type": [
            "string",
            "number"
          ],
          "description": "Расчётный счёт, 20 цифр"
        },
        "corr_account": {
          "type": [
            "string",
            "number"
          ],
          "description": "Корреспондентский счёт банка, 20 цифр"
        }
      },
      "additionalProperties": false
    }
    arguments 56 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 ffcbd9df73abf512.

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