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

prismfact

https://prismfact.com

Registry code: da6004cd1d204cdb

api record

Реестровые факты о субъектах МСП Томской области. Якорь — ИНН. У каждого значения источник, дата и способ перепроверить. Состояния между вызовами нет: каждый ответ полон сам по себе.

endpoint
https://prismfact.com/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 prismfact live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is prismfact free to use?
Yes — the hub reached it with no key and no payment.
What tools does prismfact have?
5 tools: prism_nearby, prism_ask, prism_needs, prism_answer, prism_find.
Is prismfact 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 98.4%· all time 98.4%

latency
266ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 304 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· HTTP 503
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • look up a company by tax id
  • find small businesses by activity and region
  • find businesses near a location
takes → gives
text, data → data
tools
5 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 5 tools
1 open 4 never probed 1 of 5 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.

  • prism_find reads open 11h ago

    Кто есть на территории по виду деятельности, размеру, налоговому режиму, выручке, задолженности. В каждом ответе знаменатель — сколько всего субъектов на этой территории, без него доля бессмысленна. Проверку продают все, обнаружение не продаёт никто.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "q": {
          "type": "string",
          "description": "подстрока в названии"
        },
        "sort": {
          "type": "string",
          "description": "name, okved, since, headcount, revenue, tax_debt"
        },
        "type": {
          "type": "string",
          "description": "UL или IP"
        },
        "limit": {
          "type": "string"
        },
        "okved": {
          "type": "string",
          "description": "код или его начало"
        },
        "offset": {
          "type": "string"
        },
        "regime": {
          "type": "string",
          "description": "налоговый режим"
        },
        "category": {
          "type": "string",
          "description": "1 микро, 2 малое, 3 среднее; принимаются и слова"
        },
        "district": {
          "type": "string",
          "description": "муниципальный район"
        },
        "settlement": {
          "type": "string",
          "description": "населённый пункт"
        },
        "revenue_min": {
          "type": "string"
        },
        "has_tax_debt": {
          "type": "string",
          "description": "true или false"
        },
        "changed_since": {
          "type": "string",
          "description": "дата среза, только изменившиеся"
        },
        "headcount_min": {
          "type": "string"
        }
      }
    }
    arguments 58 lines
  • prism_nearby reads unknown never probed

    Слой карты, а не реестр: заведения с вывесками и координатами. Связь вывески с ИНН нигде не установлена и отдаётся как гипотеза с указанием, чем её подтвердить. Реестр на этот вопрос ответить не может — координат в нём нет.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lat",
        "lon"
      ],
      "properties": {
        "q": {
          "type": "string"
        },
        "lat": {
          "type": "number"
        },
        "lon": {
          "type": "number"
        },
        "limit": {
          "type": "string"
        },
        "category": {
          "type": "string"
        },
        "radius_m": {
          "type": "string",
          "description": "по умолчанию 500"
        }
      }
    }
    arguments 28 lines
  • prism_ask reads unknown never probed

    Всё, что известно про ИНН, с источником и датой у каждого значения. Отсутствие размечено пятью способами: found, none, unknown, not_provided, withheld — так видно, повторять ли вопрос и куда идти дальше. Принимает до ста ИНН через запятую.

    mcp-tool

    {
      "type": "object",
      "required": [
        "inn"
      ],
      "properties": {
        "inn": {
          "type": "string",
          "description": "ИНН, можно несколько через запятую"
        },
        "want": {
          "type": "string",
          "description": "необязательный список полей через запятую"
        }
      }
    }
    arguments 16 lines
  • prism_needs reads unknown never probed

    Список дыр, нарисованный чужими вопросами: что спрашивали и на что мы не ответили. Показывается то, о чём спросили не меньше трёх разных сторон. Дыру можно закрыть, принеся факт — он проходит те же ворота записи, что и наши собственные данные.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "string",
          "description": "окно, по умолчанию 30"
        }
      }
    }
    arguments 10 lines
  • prism_answer reads unknown never probed

    Единый порядок слоёв: реестр, вывеска, учреждение, карточки людей, списки города, карта, справочник контактов. Один вопрос — один ответ, тот же самый, что получает человек в боте и на сайте. Списком не отдаётся: карточки людей (что предлагают, что ищут) отвечают только на прямой вопрос, обход закрыт даже здесь — это единственный наш актив, ценность которого мы сами ещё не измерили. Объявления досок в этот инструмент не входят — право на переотдачу не оформлено.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "вопрос словами, как человеку"
        },
        "city": {
          "type": "string",
          "description": "по умолчанию Асино"
        }
      }
    }
    arguments 16 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 da6004cd1d204cdb.

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

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.