SONAR: KYB due diligence
Company register lookups and KYB checks: registries, sanctions, PEP, offshore leaks, adverse media.
Description from the maker (original English)
One MCP server for Polish legal data - courts, legislation, KRS, tax, KIO, UODO via 4 unified tools
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"prawo-pl": {
"command": "uvx",
"args": [
"prawo-pl-mcp"
]
}
}
}Run this in your terminal
claude mcp add prawo-pl -- uvx prawo-pl-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"prawo-pl": {
"command": "uvx",
"args": [
"prawo-pl-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"prawo-pl": {
"type": "stdio",
"command": "uvx",
"args": [
"prawo-pl-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account matematicsolutions, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.4) reached the registry 44 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: SONAR: KYB due diligence, DutyKit, Agent Data Tools: Company, compliance and checks
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Company register lookups and KYB checks: registries, sanctions, PEP, offshore leaks, adverse media.
EU business duties for AI agents: legal obligations with sources and pre-checks (DE, LU, EU)
38 tools: OFAC sanctions, counterparty checks, company, domain, email. 25 free calls.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
One MCP server for Polish legal data.
Ten independent connectors - case law, legislation, the company register, tax rulings, public procurement, data-protection decisions, plus EU extras - behind five tools. Each connector stays a separate package with its own repository; this server spawns them on demand and translates between their conventions.
"Prawo" is Polish for "law"; the name follows yargi-mcp's move of naming a country server in its own language.
The connectors cover Polish legal data well, but as separate MCP servers, one per database - ten installs and ten config entries before the first question. yargi-mcp showed the fix for Turkish law: 16 institutions, one server. prawo-pl-mcp does the same for Poland:
pl_list_sources, pl_search, pl_get_document, pl_call and pl_coverage - fewer tool schemas means less context spent before the LLM starts working.dateFrom here, date_from there, pages counted from 0 or from 1 depending on the repo. Here page is always 1-based and dates are always date_from/date_to (YYYY-MM-DD); the translation happens inside. One name per concept applies to the aggregator's own tools too: page is the page parameter of both pl_search and pl_get_document (page_number still works as a deprecated alias), and pl_call takes arguments or its alias args.native_params - the native parameter name each unified one maps to for that source, so article_number (eu-compliance) is visible without spawning the connector or reading an upstream error. pl_call checks the names it was given against the connector's own schema and says which one it meant.npx -y / uvx, downloaded on the first call to a given source and kept alive afterwards. A source that cannot start reports a readable error while the rest keep working.isap) get the page forwarded natively and are reported as pagination: "native" - the aggregator does not re-cut an already-cut page and does not invent a total_pages it cannot know.| Source id | What | Institution / database | Connector | Runtime |
|---|---|---|---|---|
saos | Case law: common courts, Supreme Court, Constitutional Tribunal + citator | SAOS | mcp-saos | npx |
nsa | Case law: administrative courts (NSA + 16 WSA) | CBOSA | mcp-nsa | npx |
isap | Legislation: Dziennik Ustaw + Monitor Polski, 96k+ acts | Sejm ELI API | mcp-isap | npx |
krs | Company register: extracts, history, board composition | KRS API (Ministry of Justice) | mcp-krs | npx |
eureka | Tax rulings: 550k+ individual interpretations | EUREKA (Ministry of Finance) | mcp-eureka | npx |
kio | Public procurement: National Appeal Chamber rulings | orzeczenia.uzp.gov.pl | kio-orzeczenia-mcp | uvx |
uodo | GDPR enforcement: Polish DPA decisions, fines, stats | orzeczenia.uodo.gov.pl | uodo-orzeczenia-mcp | uvx |
eu-sparql | EU law: EUR-Lex by CELEX, CJEU by ECLI, GDPRhub | Cellar SPARQL | mcp-eu-sparql | npx |
eu-compliance | 14 EU regulations offline (GDPR, AI Act, DORA, NIS2...) | Local SQLite corpus | mcp-eu-compliance | npx |
legalize | Law-as-git: 32 jurisdictions, versioned by commit | legalize-dev | legalize-mcp | uvx |
Polish sources are tagged group: pl, EU extras group: eu - filter with pl_list_sources(group="pl").
| Tool | What it does |
|---|---|
pl_list_sources | Catalog of sources (no subprocess spawned). With source_id: live tool schemas of one connector. |
pl_search | Search any source with normalized parameters; source-specific filters via extra. |
pl_get_document | Full document by identifier (judgment id, ELI, KRS number, signature...), paginated. |
pl_call | Any native tool of any connector: citator, DPA statistics, board composition, regulation comparison... |
pl_coverage | Declare what this connector covers, when each family was captured, and - explicitly - what it does NOT cover. Every gap carries a fallback. |
The typical flow an LLM follows (spelled out in the server's instructions): pl_list_sources → pl_search → pl_get_document, with pl_call for the specialized tools each connector brings.
Requires Python ≥ 3.11 plus the runtimes of the sources you use: Node.js ≥ 18 for npx sources, uv for uvx sources. If a runtime is missing, its sources report source_unavailable and the rest work.
claude mcp add pl-legal -- uvx prawo-pl-mcp
{
"mcpServers": { "pl-legal": { "command": "uvx", "args": ["prawo-pl-mcp"] } } }
uvicorn prawo_pl_mcp.asgi:app --host 0.0.0.0 --port 8000
Open by default (public, read-only data). Set PRAWO_PL_MCP_API_KEY to require X-API-Key: or Authorization: Bearer on every request.
| Env | Default | Meaning |
|---|---|---|
PRAWO_PL_MCP_CMD_ | - | Override the spawn command for a source, e.g. PRAWO_PL_MCP_CMD_SAOS="node C:/dev/mcp-saos/dist/index.js" for a local checkout. = source id, uppercase, - → _. |
PRAWO_PL_MCP_INIT_TIMEOUT | 180 | Seconds allowed for a connector's first start (includes package download). |
PRAWO_PL_MCP_TIMEOUT | 90 | Seconds per tool call after startup. |
PRAWO_PL_MCP_AUDIT_DIR | ~/.matematic/audit | Where the JSONL audit log goes. |
PRAWO_PL_MCP_API_KEY | - | ASGI mode only: require this API key (dual-channel). |
The aggregator is a thin proxy (ADR 0001). Connectors are not imported, vendored or forked; the aggregator speaks MCP to them over stdio the same way any client would. The whole layer is a source registry (one dataclass entry per connector), a lazy subprocess pool, a parameter translator and a paginator. Adding a source means adding a registry entry.
LLM client ──MCP──▶ prawo-pl-mcp ──MCP/stdio──▶ npx @matematicsolutions/mcp-saos
│ ──MCP/stdio──▶ uvx kio-orzeczenia-mcp │ ──MCP/stdio──▶ ... (spawned on first use) └─ registry + param mapping + 5000-char pagination
Every call lands in a JSONL audit log (timestamp, tool, source, parameter hash, latency - never document content).
git clone https://github.com/matematicsolutions/prawo-pl-mcp && cd prawo-pl-mcp
uv sync --extra dev uv run pytest # offline tests: registry, dispatch mapping, pagination, drift uv run prawo-pl-mcp # stdio server
Apache-2.0. Individual connectors carry their own licenses (MIT or Apache-2.0), their own rate limits and their own terms toward upstream databases - the aggregator adds no caching and no transformation beyond pagination, so each connector's constraints apply unchanged.