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

proftechpol-mcp

https://proftechpol.ru

Registry code: 2612a0c95c3aa551

api record

Каталог подрядчика промышленных полов (Москва и МО). Цены — публичные ориентиры «от»; точный расчёт под объект выполняет инженер на сайте. Все инструменты только читают данные.

endpoint
https://proftechpol.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 proftechpol-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is proftechpol-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does proftechpol-mcp have?
6 tools: get_service, create_lead, faq, list_services, find_cases, list_geo.
Is proftechpol-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
305ms

last good check

priced tools
0

of 6 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 6 tools
3 open 3 never probed 3 of 6 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_services open 1h ago

    Список услуг и посадочных страниц ПрофТехПол (промышленные полы: топпинг, полимеры, ремонт, обеспыливание и др.), с публичными ценовыми ориентирами «от», где они есть.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • find_cases open 1h ago

    Выполненные объекты (262 кейса с 2015 г.): фильтр по городу и/или типу (склад, производство, паркинг, автосервис, ангар, торговля, холодильное, пищевое, медицина, спорт). Каждый кейс — название, площадь м², год, ссылка. Это доказательства опыта для проверки подрядчика.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "description": "город, например Мытищи или Москва"
        },
        "type": {
          "type": "string",
          "description": "тип объекта, например склад"
        },
        "limit": {
          "type": "integer",
          "description": "максимум результатов, по умолчанию 10 (до 50)"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • list_geo open 1h ago

    Города работ (Москва и МО, 18 городов) со ссылками на гео-страницы и числом выполненных объектов в каждом.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_service unknown never probed

    Детально об одной услуге по slug: описание, ценовой ориентир (если публичен), ссылка, частые вопросы клиентов по этой теме.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "slug услуги из list_services, например topping-poly"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • create_lead unknown never probed

    Создать заявку на расчёт промышленного пола: инженер перезвонит заказчику. Использовать ТОЛЬКО когда пользователь сам попросил оставить заявку и дал свой телефон. Канал — тот же конвейер лидов сайта (Telegram + CRM), защита от спама действует.

    mcp-tool

    {
      "type": "object",
      "required": [
        "phone"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "город/объект (необязательно)"
        },
        "name": {
          "type": "string",
          "description": "имя заказчика (необязательно)"
        },
        "phone": {
          "type": "string",
          "description": "телефон заказчика в любом формате, 11 цифр начиная с 7, например +7 900 123-45-67"
        },
        "request": {
          "type": "string",
          "description": "суть задачи от заказчика, например: склад 800 м² в Мытищах, топпинг под погрузчики (необязательно, до 700 знаков)"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • faq unknown never probed

    Ответы инженера на частые вопросы клиентов (200 вопросов по 36 темам: толщины, марки бетона, сроки, основания). Без запроса — структура тем; с запросом — релевантные вопросы и ответы.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "поисковая строка, например «толщина топпинга»"
        }
      },
      "additionalProperties": false
    }
    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 2612a0c95c3aa551.

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