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.

pl.nipregon/nipregon

REMOTE · API.NIPREGON.PL · SCANNED SEP 21

Polish company registry: 4.4M firms, KRS/REGON data, VAT white list checks, financial statements

Available components

0 this week 83 Trust /100
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 Security74
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 944 tokens (~134/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the pl.nipregon/nipregon MCP server?

pl.nipregon/nipregon is a hosted endpoint at https://api.nipregon.pl/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 · api.nipregon.pl

# add to Claude Code
claude mcp add --transport http pl-nipregon-nipregon 'https://api.nipregon.pl/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "pl-nipregon-nipregon": {
      "url": "https://api.nipregon.pl/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pl-nipregon-nipregon": {
      "type": "http",
      "url": "https://api.nipregon.pl/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.pl-nipregon-nipregon]
url = "https://api.nipregon.pl/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pl-nipregon-nipregon": {
      "type": "remote",
      "url": "https://api.nipregon.pl/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pl-nipregon-nipregon --url 'https://api.nipregon.pl/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pl-nipregon-nipregon:
    url: "https://api.nipregon.pl/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pl-nipregon-nipregon": {
      "Transport": "http",
      "Url": "https://api.nipregon.pl/mcp"
    }
  }
}
# add to Vellum
assistant mcp add pl-nipregon-nipregon -t streamable-http -u 'https://api.nipregon.pl/mcp'
// mcp.json
{
  "mcpServers": {
    "pl-nipregon-nipregon": {
      "type": "http",
      "url": "https://api.nipregon.pl/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 30 Aug 26 0
    • Stability: 0.97 → pass security
  • 29 Aug 26 0
    • Stability: pass → 0.97 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 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
  • 1 Aug 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
  • 31 Jul 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 Sept 2026 · Probed https://api.nipregon.pl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nipregon.pl CN=YE2,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA384 6f650f53068382a3d82711d2620f1e98bd3
SANs: *.nipregon.pl, nipregon.pl
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.nipregon.pl. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pl. present 2782 8 Verified
nipregon.pl. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.nipregon.pl/mcp Verified 200
http (plaintext) http://api.nipregon.pl/mcp HTTPS enforced 301 https://api.nipregon.pl/mcp
MCP tools · 7 exposed · ~832 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
check_risk_flags ~142

Compliance red-flag check for a Polish company (legal entity) by NIP. USE THIS for KYC/AML or before onboarding a counterparty: returns whether the company appears on Polish or EU sanctions lists (as the sanctioned subject) and whether it has a public warning from the KNF (Polish Financial Supervision Authority). A KNF warning is a notice filed with the prosecutor, not a conviction: apply the presumption of innocence. Legal entities only (sole traders are out of scope). Exact match on NIP/KRS/REGON. Read-only.

NameTypeReqDescription
nipstringyesPolish tax ID (NIP), 10 digits

No output schema declared.

No examples provided.

check_vat_whitelist ~133

Check a Polish company's VAT status in the Ministry of Finance taxpayer register (the 'white list', biała lista KAS) and, optionally, whether a given bank account number is registered to that company. USE THIS before paying an invoice: in Poland, paying over PLN 15,000 to an account outside the white list has tax consequences. Returns VAT status and account-match result. Live query to the official KAS register. Read-only.

NameTypeReqDescription
accountstringPolish bank account number (26 digits), optional
nipstringyesPolish tax ID (NIP), 10 digits

No output schema declared.

No examples provided.

get_company ~118

Get the full registry profile of a Polish company by its NIP (10-digit tax ID). USE THIS when the user gives a NIP and wants company details, address, board members, or registry status. Returns address, legal form, status, KRS, REGON, PKD activity codes, board members (names from the public KRS register) and VAT status. Data from KRS, REGON and CEIDG public registers. Read-only.

NameTypeReqDescription
nipstringyesPolish tax ID (NIP), 10 digits

No output schema declared.

No examples provided.

get_financials ~96

Get yearly financial statements of a Polish company by NIP, as filed with the National Court Register (KRS). USE THIS when the user asks about a company's revenue, profit, assets or financial results. Returns per-year revenue, net profit, total assets, equity and liabilities. Data from financial statements (RDF/KRS). Read-only.

NameTypeReqDescription
nipstringyesPolish tax ID (NIP), 10 digits

No output schema declared.

No examples provided.

get_lei ~111

Get the Legal Entity Identifier (LEI, ISO 17442) of a Polish company (legal entity) by NIP, from the GLEIF register. USE THIS when the user needs a company's LEI for cross-border or financial-market reporting (MiFID, EMIR, payments). Returns the LEI, the registered legal name and the LEI status. Coverage is partial. Legal entities only. Read-only.

NameTypeReqDescription
nipstringyesPolish tax ID (NIP), 10 digits

No output schema declared.

No examples provided.

get_public_tenders ~119

Get Polish public-procurement contracts awarded to a company (legal entity) by NIP, as published in the Public Procurement Bulletin (BZP). USE THIS for due diligence or sales intelligence when the user asks what public tenders or government contracts a company has won. Returns up to 25 most recent awards (subject, contracting authority, city, date, value) plus the total count and total value across all awards. Legal entities only. Read-only.

NameTypeReqDescription
nipstringyesPolish tax ID (NIP), 10 digits

No output schema declared.

No examples provided.

search_company ~113

Search Polish companies by name (fuzzy match). USE THIS when the user asks to find a Polish company, look up a firm by name, or get its NIP/KRS/REGON. Returns NIP, KRS, city, status and a profile URL. Data from the Polish court (KRS) and statistical (REGON) registers. Read-only.

NameTypeReqDescription
limitintegerMax results (1-10, default 5)
querystringyesCompany name or part of it

No output schema declared.

No examples provided.

Common questions

What is the pl.nipregon/nipregon MCP server?

pl.nipregon/nipregon is an MCP server listed in the public MCP registry as pl.nipregon/nipregon. Polish company registry: 4.4M firms, KRS/REGON data, VAT white list checks, financial statements. This page covers its hosted endpoint (https://api.nipregon.pl/mcp).

Is the pl.nipregon/nipregon MCP server safe to use?

pl.nipregon/nipregon scores 83 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 pl.nipregon/nipregon MCP server expose?

pl.nipregon/nipregon exposes 7 tools: search_company, get_company, get_financials, check_vat_whitelist, check_risk_flags, and 2 more. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.

Does the pl.nipregon/nipregon MCP server require authentication?

No. We connected to pl.nipregon/nipregon without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the pl.nipregon/nipregon MCP server still maintained?

pl.nipregon/nipregon is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.