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.

skanfirmy.pl

REMOTE · SKANFIRMY.PL · SCANNED SEP 21

Verify Polish companies by NIP/KRS/REGON + EU VAT (VIES). 14 MCP tools (9 no-key).

Available components

+4 this week 75 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 Security57
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1581 tokens (~112/item across 14 items; 14 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 Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "unobserve_nip" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the skanfirmy.pl MCP server?

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

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

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 18 Sept 26 0
    • Server version: 1.1.1 → 1.1.2 functional
  • 17 Sept 26 +1

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

  • 15 Sept 26 +1
    • Server version: 1.0.0 → 1.1.1 functional
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 8 Sept 26 +1

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

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://skanfirmy.pl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=skanfirmy.pl CN=WE1,O=Google Trust Services,C=US 17 Sept 2026 16 Dec 2026 ECDSA 256 ECDSA-SHA256 d3fa53becdfc20650eb9d5c2e26518d4
SANs: skanfirmy.pl
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of skanfirmy.pl. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pl. present 2782 8 Verified
skanfirmy.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://skanfirmy.pl/mcp Verified 200
http (plaintext) http://skanfirmy.pl/mcp HTTPS enforced 301 https://skanfirmy.pl/mcp
MCP tools · 14 exposed · ~1,424 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
changes_since ~145

Return changes (VAT status, bank accounts, or registry data — name, address, KRS, REGON — from the White List) detected since a given date for the NIPs you monitor. The field property is one of: status_vat, account_added, account_removed, name, address, krs, regon. A polling channel for agents. Requires a skanfirmy API key.

NameTypeReqDescription
api_keystringskanfirmy API key (optional, if not in the header).
sincestringISO date/timestamp (e.g. 2026-08-01). Returns changes since that date. Defaults to the beginning.

No output schema declared.

No examples provided.

generuj_mikrorachunek ~58

Generate the individual tax micro-account (for PIT/CIT/VAT payments) from a NIP or PESEL.

NameTypeReqDescription
identyfikatorstringyesNIP (10 digits) or PESEL (11 digits).

No output schema declared.

No examples provided.

list_observations ~104

Return the list of NIPs you monitor, with their current VAT status and last-checked date. Each entry keeps the raw Ministry of Finance literal in status_vat and, when a status is known, adds derived language-neutral fields vat_active (boolean) and status_vat_code (active/exempt/not_registered). Requires a skanfirmy API key.

NameTypeReqDescription
api_keystringskanfirmy API key (optional, if not in the header).

No output schema declared.

No examples provided.

oblicz_odsetki ~167

Calculate statutory or commercial (B2B) late-payment interest, broken down by NBP reference-rate periods.

NameTypeReqDescription
dataDostringyesActual payment date, format YYYY-MM-DD.
dataOdstringyesPayment due date, format YYYY-MM-DD.
kwotanumberyesOverdue amount in PLN.
typstringyeskc = statutory late-payment interest (Civil Code art. 481, NBP reference rate + 5.5 pp); h10 = commercial B2B transactions, non-public debtor (NBP reference rate on 1 Jan / 1 Jul + 10 pp); h8 = comme…

No output schema declared.

No examples provided.

observe_nip ~124

Add a NIP to monitoring. You get notified (via changes_since or email) when its VAT status, bank account, or registry data shown on the Ministry of Finance White List (name, address, KRS, REGON) changes. Requires a skanfirmy API key (Authorization: Bearer, or the api_key argument). Free plan: up to 10 NIPs.

NameTypeReqDescription
api_keystringskanfirmy API key (if not provided in the Authorization header).
nipstringyes10-digit NIP to monitor.

No output schema declared.

No examples provided.

set_webhook ~135

Set (or clear) a push webhook URL for your monitoring, instead of or in addition to polling. When we detect a change for a monitored NIP, we send a POST signed with HMAC-SHA256 (X-Skanfirmy-Signature header). Returns the secret ONCE. Pass an empty url to disable. Requires a skanfirmy API key. Public https addresses only (port 443).

NameTypeReqDescription
api_keystringskanfirmy API key (optional, if not in the header).
urlstringPublic https URL of the receiver (empty = disable the webhook).

No output schema declared.

No examples provided.

sprawdz_lista_nip ~131

Bulk-check up to 30 NIPs in one call to the Ministry of Finance VAT White List: VAT status, bank accounts, REGON, KRS and address of each entity. For verifying a portfolio of counterparties. Ministry limits: max 30 NIPs per call, about 500 bulk queries/day per IP. Does not fetch full KRS data (use sprawdz_nip for individual entities).

NameTypeReqDescription
nipyarrayyesList of NIPs (1 to 30). Each 10-digit with a valid checksum. Invalid NIPs are returned separately in the invalidInput field.

No output schema declared.

No examples provided.

sprawdz_nip ~50

Check VAT status (VAT White List / Biała Lista) and KRS data for a Polish company by NIP.

NameTypeReqDescription
nipstringyes10-digit Polish NIP (tax ID).

No output schema declared.

No examples provided.

sprawdz_rachunek ~84

Check whether a bank account number (NRB) appears in the VAT White List for a given NIP. Due diligence for payments above PLN 15,000.

NameTypeReqDescription
nipstringyes10-digit NIP of the counterparty.
numerRachunkustringyes26-digit bank account number (NRB), without the PL prefix.

No output schema declared.

No examples provided.

sprawdz_regon ~91

Look up entity data in the REGON register (Statistics Poland / GUS BIR) by NIP: REGON number, official name, legal form (legal or natural person), full address (voivodeship, county, municipality). Covers ALL entities, including sole proprietors that are not in the KRS.

NameTypeReqDescription
nipstringyes10-digit Polish NIP (tax ID).

No output schema declared.

No examples provided.

sprawdz_vies ~63

Validate a counterparty's EU VAT number in the VIES system (European Commission).

NameTypeReqDescription
countryCodestringyesTwo-letter EU country code (e.g. DE, IE, FR).
vatNumberstringyesVAT number without the country prefix.

No output schema declared.

No examples provided.

szukaj_katalog_api ~151

Search otwarteAPI.pl, a catalog of public Polish and EU APIs (VAT, KRS, GUS, NBP, ECB, Eurostat and more). Returns matching entries with a link to each API's official docs. An empty query returns the whole catalog (optionally narrowed by scope or topic).

NameTypeReqDescription
tematstringNarrow to a specific catalog tag, e.g. "firmy" or "dane-statystyczne". Optional.
zapytaniestringNatural-language query, e.g. "euro exchange rate" or "weather data". Optional.
zasiegstringNarrow to Polish (PL) or EU APIs. Optional.

No output schema declared.

No examples provided.

szukaj_pkd ~57

Search PKD 2025 business activity codes by activity name or code number.

NameTypeReqDescription
zapytaniestringyesActivity name (e.g. "software") or PKD code (e.g. "62.01").

No output schema declared.

No examples provided.

unobserve_nip ~64

Remove a NIP from monitoring. Requires a skanfirmy API key.

NameTypeReqDescription
api_keystringskanfirmy API key (optional, if not in the header).
nipstringyes10-digit NIP to remove from monitoring.

No output schema declared.

No examples provided.

Common questions

What is the skanfirmy.pl MCP server?

skanfirmy.pl is an MCP server listed in the public MCP registry as io.github.bartosz-kuc/skanfirmy. Verify Polish companies by NIP/KRS/REGON + EU VAT (VIES). 14 MCP tools (9 no-key). This page covers its hosted endpoint (https://skanfirmy.pl/mcp).

Is the skanfirmy.pl MCP server safe to use?

skanfirmy.pl scores 75 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 skanfirmy.pl MCP server expose?

skanfirmy.pl exposes 14 tools: sprawdz_nip, sprawdz_lista_nip, sprawdz_regon, sprawdz_vies, sprawdz_rachunek, and 9 more. Their descriptions and schemas cost roughly 1,424 tokens of context every time the server is loaded.

Does the skanfirmy.pl MCP server require authentication?

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

Is the skanfirmy.pl MCP server still maintained?

skanfirmy.pl 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.