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

htmlweb

https://mcp.htmlweb.ru

Registry code: 9a6ba140250657d8

api record

RU org INN/OGRN, banks, geo, email, WHOIS, phone, inflect, MCC. Bearer api_key, 20 free/day.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.htmlweb.ru/
protocol
streamable-http ·2024-11-05
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 htmlweb live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is htmlweb free to use?
Yes — the hub reached it with no key and no payment.
What tools does htmlweb have?
9 tools: register_agent, bind_payment_card, api_catalog, api_call, create_topup_crypto, create_topup_card, acp_checkout, charge_saved_card, ….
Is htmlweb 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
782ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 294 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • look up russian companies by inn or ogrn
  • call htmlweb data api methods
  • top up api balance by card or crypto
takes → gives
text, data → data, payments
tools
2 reads4 changes data2 moves money1 effect unclear
_ 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 9 tools
1 open 8 never probed 1 of 9 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.

  • get_pricing reads open 7h ago

    Тарифы, пакеты и commerce.json. Бесплатно.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": []
    }
    arguments 5 lines
  • register_agent changes data unknown never probed

    Создать api_key агента без регистрации на сайте. Без Authorization. До 2/сутки с IP; повтор с того же IP за день возвращает существующий ключ. Без бесплатной суточной квоты (adm=0).

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "label": {
          "type": "string",
          "description": "Метка агента (опционально)"
        }
      }
    }
    arguments 10 lines
  • bind_payment_card changes data unknown never probed

    Привязать карту к ключу (Robokassa Recurring). Один раз 3-D Secure; дальше charge_saved_card.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": []
    }
    arguments 5 lines
  • api_catalog reads unknown never probed

    Каталог штатного API: классы и pub_* (как /json/{obj}/help). Без obj — список классов; с obj — методы. Баланс: money/get_limit; пакет: money/set_limit.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "obj": {
          "type": "string",
          "description": "ai|calendar|convert|geo|mail|mnp|money|service|validator"
        }
      }
    }
    arguments 10 lines
  • api_call unknown never probed

    Вызов штатного REST: Get::apiParam → Class::pub_m. Эквивалент https://htmlweb.ru/json/{obj}/{m}. Баланс: obj=money m=get_limit; пакет с баланса: m=set_limit + set_limit=N.

    mcp-tool

    {
      "type": "object",
      "required": [
        "obj",
        "m"
      ],
      "properties": {
        "m": {
          "type": "string",
          "description": "m"
        },
        "obj": {
          "type": "string",
          "description": "obj"
        },
        "params": {
          "type": "string",
          "description": "JSON-объект прочих параметров метода (или передайте их плоско рядом с obj/m)"
        }
      }
    }
    arguments 21 lines
  • create_topup_crypto changes data unknown never probed

    Крипто-депозит на баланс ключа. amount_rub мин. 500, ticker: usdttrc20, btc…

    mcp-tool

    {
      "type": "object",
      "required": [
        "amount_rub",
        "ticker"
      ],
      "properties": {
        "ticker": {
          "type": "string",
          "description": "ticker"
        },
        "amount_rub": {
          "type": "string",
          "description": "amount_rub"
        }
      }
    }
    arguments 17 lines
  • create_topup_card changes data unknown never probed

    Ссылка Robokassa для пополнения баланса ключа (3-D Secure). amount_rub мин. 50.

    mcp-tool

    {
      "type": "object",
      "required": [
        "amount_rub"
      ],
      "properties": {
        "amount_rub": {
          "type": "string",
          "description": "amount_rub"
        }
      }
    }
    arguments 12 lines
  • acp_checkout moves money unknown never probed

    ACP checkout: create/get/complete/cancel. Autopay: htmlweb.prepaid.wallet | htmlweb.robokassa.rebill.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "action": {
          "type": "string",
          "description": "create|get|complete|cancel|update"
        },
        "ticker": {
          "type": "string",
          "description": "крипто"
        },
        "requests": {
          "type": "string",
          "description": "пакет запросов"
        },
        "amount_rub": {
          "type": "string",
          "description": "пополнение"
        },
        "handler_id": {
          "type": "string",
          "description": "htmlweb.prepaid.wallet|htmlweb.robokassa.rebill|htmlweb.robokassa.card|htmlweb.bybit.crypto"
        },
        "line_items": {
          "type": "string",
          "description": "ACP line_items[]"
        },
        "session_id": {
          "type": "string",
          "description": "cs_…"
        },
        "payment_data": {
          "type": "string",
          "description": "ACP payment_data"
        }
      }
    }
    arguments 38 lines
  • charge_saved_card moves money unknown never probed

    Автосписание с привязанной карты на баланс (без 3-D Secure). amount_rub мин. 50.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "amount_rub": {
          "type": "string",
          "description": "Сумма, руб."
        }
      }
    }
    arguments 10 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 9a6ba140250657d8.

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

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.