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.

mcp-sudact

PYPI · ATOMNO-MCP-SUDACT

Court practice and FAS case cards via hosted API. Coverage depends on the connected service.

Available components

−5 this week 77 Trust /100

Last scanned (7 hours ago)

Scores higher than 74% of PyPI servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 21 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 933 tokens (~186/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 4 Nov 26 +14
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Tool coverage: 86% → 81% ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 217 → 186 ▲ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.1.10 → 0.2.0 functional
  • 3 Nov 26 −17
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: 100% → 86% ▼ functional
    • Schema quality: 283 → 217 ▲ functional
    • Schema quality: excellent → good functional
    • Package version: 0.1.8 → 0.1.10 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 22 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
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 5 Nov 2026 · Analysed pypi/atomno-mcp-sudact@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 21 packages
Packages resolved 21
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~825 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
get_citation ~87

Текст акта или карточки; полный текст доступен не для каждой записи. Нужен url/case_id. Анонимизация и её ограничения определяются backend.

NameTypeReqDescription
anonymize_levelstring––
case_id––case_id из выдачи, включая fas:.
include_full_textboolean––
url––URL из выдачи поиска.

Structured output declared, but exposes no named fields.

No examples provided.

get_search_capabilities ~33

Текущие разделы, поддержка фильтров и доступность page на подключённом сервере.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

resolve_court_name ~120

Кандидаты судов из ограниченной выборки карточек, с явной неоднозначностью. Если query и case_number не заданы, name становится текстовым запросом. Это не полный справочник. Один поиск, обычный учёт вызова и возвращённых карточек.

NameTypeReqDescription
case_number–––
court_typestringyesОдин раздел: arbitr/soyu/vs.
limitinteger––
namestringyesПолное имя или фрагмент имени суда.
querystring––

Structured output declared, but exposes no named fields.

No examples provided.

search_cases ~429

Поиск подключённых источников с исходными provenance/предупреждениями. Доступ к soyu определяется услугой; ks не подтверждён и отклоняется. Полный корпус не гарантируется. source/collegium не поддерживаются как фильтры API. Даты/лимиты/метаданные не переписываются.

NameTypeReqDescription
case_number––Отдельный номер дела; один vs/arbitr/soyu, query необязателен.
court––Точное имя суда; только arbitr/soyu.
court_typestring–Раздел API: any/vs/arbitr/soyu/fas. Полный корпус не гарантируется.
date_from––Дата с, YYYY-MM-DD.
date_to––Дата по, YYYY-MM-DD.
fas_act_type––решение/предписание/постановление/постановление о штрафе/определение/предупреждение/жалоба/уведомление.
fas_body––Орган ФАС; court_type=any/fas.
fas_law––44-ФЗ/223-ФЗ/135-ФЗ/38-ФЗ.
instancestring–first/appeal/cassation/supervision только для soyu, проверяются по форме источника.
judge––Судья; один vs/arbitr/soyu.
limitinteger–Максимум1..50, не обещание количества.
norms––Статьи закона; способ проверки определяет backend.
page––Один vs/arbitr/soyu; page*limit<=50, без ФАС-фильтров. При обёртке норм backend422: запрос без page. Без смешения корпусов/fallback.
querystring–Текст от 3 символов; можно опустить при case_number.
region––arbitr: судебный округ; soyu: субъект РФ. Точный код или имя текущей формы; значения зависят от раздела.

Structured output declared, but exposes no named fields.

No examples provided.

search_fas_decisions ~156

Карточки базы решений ФАС через /v1/search court_type=fas. Не обещает полный текст решения. Источник, дата сведений и предупреждения сохраняются. Текст карточки можно запросить через get_citation.

NameTypeReqDescription
act_type––Вид акта ФАС, например решение.
body––Орган ФАС.
date_from––Дата карточки с, YYYY-MM-DD.
date_to––Дата карточки по, YYYY-MM-DD.
law––44-ФЗ/223-ФЗ/135-ФЗ/38-ФЗ.
limitinteger––
querystringyesТекст или номер дела ФАС.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the mcp-sudact server?

mcp-sudact runs locally as a PyPI package, launched with uvx atomno-mcp-sudact. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · atomno-mcp-sudact

# add to Claude Code
claude mcp add atomno-mcp-mcp-sudact -- uvx atomno-mcp-sudact
Common questions

What is the mcp-sudact server?

mcp-sudact is listed in the public MCP registry as io.github.atomno-mcp/mcp-sudact. Court practice and FAS case cards via hosted API. Coverage depends on the connected service. This page covers its PyPI package (atomno-mcp-sudact).

Is the mcp-sudact server safe to use?

mcp-sudact scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 mcp-sudact server expose?

mcp-sudact exposes 5 tools: search_cases, get_search_capabilities, resolve_court_name, search_fas_decisions, get_citation. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.

Is the mcp-sudact server still maintained?

mcp-sudact is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the mcp-sudact server under?

mcp-sudact declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.