Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PrismFact

REMOTE · PRISMFACT.COM

Факты о бизнесе Томской области по ИНН: деньги, налоги, долг, статус. С источником и датой.

Available components

−62 this week 16 Trust /100

Last scanned (19 hours ago)

Scores higher than 3% of remote servers

Unreachable for 6 days in a row. Last reached 15 Nov 2026.

Category CRM and Sales

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 20 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 19 Nov 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://prismfact.com/mcp

TLS unreached
DNSSEC insecure

Validation of prismfact.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
prismfact.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://prismfact.com/mcp Unreachable
http (plaintext) http://prismfact.com/mcp HTTPS enforced
MCP tools · 5 exposed · ~728 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
prism_answer ~156

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

NameTypeReqDescription
citystring–по умолчанию Асино
qstringyesвопрос словами, как человеку

No output schema declared.

No examples provided.

prism_ask ~111

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

NameTypeReqDescription
innstringyesИНН, можно несколько через запятую
wantstring–необязательный список полей через запятую

No output schema declared.

No examples provided.

prism_find ~243

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

NameTypeReqDescription
categorystring–1 микро, 2 малое, 3 среднее; принимаются и слова
changed_sincestring–дата среза, только изменившиеся
districtstring–муниципальный район
has_tax_debtstring–true или false
headcount_minstring––
limitstring––
offsetstring––
okvedstring–код или его начало
qstring–подстрока в названии
regimestring–налоговый режим
revenue_minstring––
settlementstring–населённый пункт
sortstring–name, okved, since, headcount, revenue, tax_debt
typestring–UL или IP

No output schema declared.

No examples provided.

prism_nearby ~127

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

NameTypeReqDescription
categorystring––
latnumberyes–
limitstring––
lonnumberyes–
qstring––
radius_mstring–по умолчанию 500

No output schema declared.

No examples provided.

prism_needs ~91

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

NameTypeReqDescription
daysstring–окно, по умолчанию 30

No output schema declared.

No examples provided.

Install

How do I install the PrismFact MCP server?

PrismFact is a hosted endpoint at https://prismfact.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · prismfact.com

# add to Claude Code
claude mcp add --transport http com-prismfact-hub 'https://prismfact.com/mcp'
Common questions

What is the PrismFact MCP server?

PrismFact is an MCP server listed in the public MCP registry as com.prismfact/hub. Факты о бизнесе Томской области по ИНН: деньги, налоги, долг, статус. С источником и датой. This page covers its hosted endpoint (https://prismfact.com/mcp).

Is the PrismFact MCP server safe to use?

PrismFact scores 16 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PrismFact MCP server expose?

PrismFact exposes 5 tools: prism_ask, prism_find, prism_nearby, prism_needs, prism_answer. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.

Does the PrismFact MCP server require authentication?

Its publisher declares no required credentials for PrismFact. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the PrismFact MCP server still maintained?

PrismFact is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 15 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the PrismFact MCP server?

VerifyMCP ran 3 checks on PrismFact, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about PrismFact: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.