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.

Karpata – company data from public registers

REMOTE · API.KARPATA.EU

Search companies in public registers: register card, live VAT risk check, risk, financials, watch.

Available components

+10 this week 82 Trust /100

Last scanned (13 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Finance and Payments

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 Security89
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1472 tokens (~122/item across 12 items; 12 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 6 Nov 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
  • 4 Nov 26 +1

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

  • 3 Nov 26 +7
    • HTTPS: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
  • 2 Nov 26 +1
    • Schema quality: 1334 → 1472 ▼ functional
    • New tool “ask” functional
  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_vat” rewrote its description, which is the text the model reads security
    • Tool “search_companies” rewrote its description, which is the text the model reads security
    • “check_vat” reworded the description of “regNo” cosmetic
    • “get_company” reworded the description of “regNo” cosmetic
    • “get_financials” reworded the description of “regNo” cosmetic
    • “get_risk” reworded the description of “regNo” cosmetic
    • “unwatch_company” reworded the description of “regNo” cosmetic
    • “verify_company” reworded the description of “regNo” cosmetic
    • “watch_company” reworded the description of “regNo” cosmetic
  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1
    • Stability: unverified → 0.03 ▲ 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 6 Nov 2026 · Probed https://api.karpata.eu/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=karpata.eu CN=WE1,O=Google Trust Services,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 1abca84256af7abe138b84c9c17eb95e
SANs: karpata.eu, api.karpata.eu, *.api.karpata.eu
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 api.karpata.eu. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
eu. DS published 35926 8 Verified
karpata.eu. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=2592000
x-content-type-options nosniff

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.karpata.eu/v1/mcp Verified 200
http (plaintext) http://api.karpata.eu/v1/mcp HTTPS enforced 301 https://api.karpata.eu/v1/mcp
MCP tools · 12 exposed · ~1,078 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
ask ~138

Ask a question in Slovak, Czech, Romanian or English about companies in Karpata's AI index (a prototype sample of firms in Slovakia, Czechia, Poland and Romania). The answer uses only register data, cites the companies as [n] with links and provenance, or says it did not find it. Questions about natural persons are refused. A question about today's VAT status or risk runs check_vat or get_risk live (charged and recorded as those). Costs credits.

NameTypeReqDescription
langstring–Optional language of the answer; default: the question's.
questionstringyesThe question, at most 500 characters.

No output schema declared.

No examples provided.

check_vat ~140

Live VAT risk before paying a supplier: SK §81 list and published accounts, CZ unreliable VAT payer (§109) and published accounts, PL white list (with date and account), RO inactive taxpayer. Stored as a verification record (see get_record). Costs credits.

NameTypeReqDescription
accountstring–PL only: the bank account (NRB) to check.
countrystringyesCountry code.
datestring–PL only: the day to check, YYYY-MM-DD.
regNostringyesRegistration number: IČO (SK, CZ), NIP or KRS number (PL), CUI (RO).

No output schema declared.

No examples provided.

get_company ~79

The basic company card from the public register: name, legal form, status, seat, main activity, VAT payer flag, with provenance. Free.

NameTypeReqDescription
countrystringyesCountry code.
regNostringyesRegistration number: IČO (SK, CZ), NIP or KRS number (PL), CUI (RO).

No output schema declared.

No examples provided.

get_financials ~70

Financial statements for up to five years with ratios (SK, CZ, RO). Costs credits.

NameTypeReqDescription
countrystringyesCountry code.
regNostringyesRegistration number: IČO (SK, CZ), NIP or KRS number (PL), CUI (RO).

No output schema declared.

No examples provided.

get_record ~45

A stored VAT check (verification record) by its id, with whether its content still matches its SHA-256.

NameTypeReqDescription
idstringyesThe record id from check_vat.

No output schema declared.

No examples provided.

get_risk ~79

Debts to the state, tax reliability, insolvency proceedings and a rule-based score with its reasons (not a credit rating). Costs credits.

NameTypeReqDescription
countrystringyesCountry code.
regNostringyesRegistration number: IČO (SK, CZ), NIP or KRS number (PL), CUI (RO).

No output schema declared.

No examples provided.

list_watched ~46

The companies your organization watches, with their current state (register status, debtor and VAT lists), the plan's watch limits and the last 200 changes detected since watching started. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

screen_name ~131

Screen a company name outside the Karpata index (a counterparty from any country) against the EU consolidated sanctions list and the US OFAC SDN list, legal entities only; optional ISO country and identifiers. A possible match is a lead to review, not a verdict. Stored as a verification record. Costs credits (Compliance data package).

NameTypeReqDescription
countrystring–Optional ISO 3166-1 alpha-2 country of the company.
identifiersarray–Optional registration or tax numbers (at most 10).
namestringyesThe company name, 2–200 characters.

No output schema declared.

No examples provided.

search_companies ~69

Find companies in Slovakia, Czechia, Poland and Romania by name or registration number. Returns the basic facts and the registration number to use with the other tools.

NameTypeReqDescription
countrystring–Country code.
limitinteger––
querystringyesCompany name or registration number.

No output schema declared.

No examples provided.

unwatch_company ~61

Stop watching a company. Idempotent; free.

NameTypeReqDescription
countrystringyesCountry code.
regNostringyesRegistration number: IČO (SK, CZ), NIP or KRS number (PL), CUI (RO).

No output schema declared.

No examples provided.

verify_company ~122

KYB: verify a legal entity as a customer or partner in one call: the register card (identification), the register status (verification), the live VAT checks and the EU / OFAC sanctions lists, with a verdict for your review (clear, review, unavailable). Stored as a verification record. Does not cover owners, representatives or persons. Costs credits.

NameTypeReqDescription
countrystringyesCountry code.
regNostringyesRegistration number: IČO (SK, CZ), NIP or KRS number (PL), CUI (RO).

No output schema declared.

No examples provided.

watch_company ~98

Start watching a company: Karpata compares it with the registers and lists every hour and records every change (status, debtor lists, VAT lists, insolvency). Idempotent. Limited by the plan's number of watched companies; free.

NameTypeReqDescription
countrystringyesCountry code.
regNostringyesRegistration number: IČO (SK, CZ), NIP or KRS number (PL), CUI (RO).

No output schema declared.

No examples provided.

Install

How do I install the Karpata – company data from public registers MCP server?

Karpata – company data from public registers is a hosted endpoint at https://api.karpata.eu/v1/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.karpata.eu

# add to Claude Code
claude mcp add --transport http eu-karpata-karpata 'https://api.karpata.eu/v1/mcp'
Common questions

What is the Karpata – company data from public registers MCP server?

Karpata – company data from public registers is an MCP server listed in the public MCP registry as eu.karpata/karpata. Search companies in public registers: register card, live VAT risk check, risk, financials, watch. This page covers its hosted endpoint (https://api.karpata.eu/v1/mcp).

Is the Karpata – company data from public registers MCP server safe to use?

Karpata – company data from public registers scores 82 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 Karpata – company data from public registers MCP server expose?

Karpata – company data from public registers exposes 12 tools: search_companies, get_company, check_vat, get_risk, verify_company, and 7 more. Their descriptions and schemas cost roughly 1,078 tokens of context every time the server is loaded.

Does the Karpata – company data from public registers MCP server require authentication?

Yes. Karpata – company data from public registers asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Karpata – company data from public registers MCP server still maintained?

Karpata – company data from public registers is still listed as active in the MCP registry. We last reached this channel on 6 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 Karpata – company data from public registers MCP server?

VerifyMCP ran 13 checks on Karpata – company data from public registers, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.