io.github.Nolpak14/getregdata
NPM · GETREGDATA-MCP
Official registry data for agents: insolvency across Europe, Poland and CEE KYB, UBO, land registers
Available components
Last scanned (5 hours ago)
Scores higher than 94% of npm servers
Category Security
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Nolpak14/getregdata). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 20181 tokens (~429/item across 47 items; 47 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 Management97
- Stability check failed: the tool surface changed between 1.2.0 and 1.4.1: 1 tool removals, 0 breaking changes, 10 additions. See how to fix → Fail
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 47 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 47 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 3 Nov 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 1.4.0 → 1.4.1 functional
- 1 Nov 26 −1
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Schema quality: 15145 → 20181 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.2.1 → 1.4.0 functional
- Package version: 1.2.0 → 1.4.0 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −4
- Malware scan: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- Stability: 0.97 → pass security
- The attested source repository moved: Nolpak14/getregdata security
- Schema quality: 334 → 398 ▼ functional
- Security disclosure: unverified → fail ▼ functional
- Package version: 1.2.0 → 1.2.1 functional
- 26 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
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 npm/getregdata-mcp@1.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Nolpak14/getregdata |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Nolpak14/getregdata/.github/workflows/release-mcp.yml@refs/tags/mcp-v1.4.1 |
| Rekor log index | 3670023910 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3c574f11cfc58efc650e9a313eed669f51dbba368b7e2e364331a95e647cab1420c9dc421d1c61c3c293f19ece006ab2d264f469b925d28f3789b98a8 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
regdata_spain_company_directory ~507
Spain Company Directory Scraper - Registro Mercantil. Scrape company data from Spain's official OpenData Registradores directory. Get NIF, officers, CNAE codes, legal form, address, and status from the Registro Mercantil - no API exists for this data. Advanced fields beyond this schema are also accepted (regdata_describe lists them).
| Name | Type | Req | Description |
|---|---|---|---|
| cnaeCode | string | – | Filter results by CNAE economic activity code. Example: '6201' (computer programming), '4711' (retail sale in non-specialized stores) |
| irusNumbers | array | – | List of IRUS numbers for direct company lookup. Skips search and goes straight to detail pages. Find IRUS in company URLs like /directorio/-/sociedad/{irus}/{company-name}. Example: '1000239977797' |
| maxItems | integer | – | Optional cap on billed dataset items returned. |
| maxResults | integer | – | Maximum number of company records to return. Default: 100. Set higher for broader searches. |
| nifNumbers | array | – | List of NIF/CIF tax identification numbers to look up. Each NIF is looked up individually for exact-match results. |
| province | string | – | Limit results to one Spanish province or one autonomous community (region). A province: its name in Spanish or the local language, common older spellings, or the INE code (1-52) - 'Madrid', 'Navarra'… |
| searchQuery | string | – | Search by company name (partial match). Example: 'Telefonica', 'Inditex', 'Banco Santander' |
No output schema declared.
No examples provided.
regdata_spain_concursal ~324
Spain Registro Público Concursal Search. Search Spain's official public insolvency register (Registro Público Concursal) by debtor name or NIF. Returns each matching party with its role - debtor, disqualified, or insolvency administrator. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).
| Name | Type | Req | Description |
|---|---|---|---|
| identifierType | string | – | Type of identifier when searching by NIF. |
| maxItems | integer | – | Optional cap on billed dataset items returned. |
| maxResults | integer | – | Maximum party records to export across all queries. The register serves results in pages, and the Actor pages through until it reaches this limit or runs out of matches. Set to 0 to export every matc… |
| name | string | – | Company name or person name to look up in the insolvency-publicity register (afectado). Leave empty when using a watchlist. |
| nif | array | – | One or more Spanish identifiers to look up. Used when search mode is "By identifier". |
| searchMode | string | – | Search by debtor/affected-party name, or by identifier (NIF/CIF/DNI/NIE). |
| watchlist | array | – | A list of names to check in one run - the monitoring use case. Overrides "name". Each name costs one search. |
No output schema declared.
No examples provided.
regdata_uae_adgm_public_register ~229
UAE ADGM Public Register Scraper - Company Data. Scrape the Abu Dhabi Global Market (ADGM) public register: company name, registration number, status, type, classification, incorporation date, address and trade names. Search by name, identifier or trade name. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).
| Name | Type | Req | Description |
|---|---|---|---|
| maxItems | integer | – | Optional cap on billed dataset items returned. |
| maxResultsPerQuery | integer | – | Maximum number of entities to extract per search query. 0 means no limit (fetch all matches). |
| minIntervalMs | integer | – | Polite delay between requests to the register. 350ms is a safe default. |
| pageSize | integer | – | How many results to fetch per request (1-100). Larger pages are faster; the default is fine for most runs. |
| searchQueries | array | yes | Entity names, registration numbers or trade names to search the ADGM public register for. Each query returns all matching entities (paginated up to the limit below). |
No output schema declared.
No examples provided.
regdata_uokik_decisions ~675
Poland UOKiK Decisions - competition and consumer protection. Search decisions of UOKiK, Poland's competition and consumer protection authority (about 22,000 decisions): merger clearances, abuse of dominant position, collective consumer interests, prohibited clauses, product safety and fuel quality, with decision number, date, named parties and practice type; includeDetails adds case signature, whether a fine was imposed, appeal status, industry (PKD) and region. Filter by party name (literal - Polish diacritics matter), practice type, decision number, case signature, industry, region, fine/appeal flags, date range or full text. The register records THAT a fine was imposed, never the amount - do not report one. Use for counterparty due diligence and regulatory-history checks on Polish companies. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).
| Name | Type | Req | Description |
|---|---|---|---|
| appealed | string | – | Whether the decision was appealed. |
| caseSignature | string | – | The case file signature, e.g. "DKK-2.430". Matches a prefix as well as a whole signature. |
| dateFrom | string | – | ISO date, YYYY-MM-DD. Note that six records in the register carry no decision date at all and are excluded by any date filter. |
| dateTo | string | – | ISO date, YYYY-MM-DD. |
| decisionNumber | string | – | The decision's own number, e.g. "DKK-171/2024". |
| fineImposed | string | – | Whether the decision imposed a fine. The register records only THAT a fine was imposed - it never publishes the amount. |
| fullText | string | – | Free text searched across the whole document index. Broader than it looks - it matches text the decision page does not display, so use the specific fields above when you can. |
| includeDetails | boolean | – | Open each decision to read its case signature, fine flag, appeal status, industry and region. Off returns only what the result list shows: number, date, party and practice type. |
| includeIncompleteRecords | boolean | – | The register holds six documents with no number, date or party. They are skipped by default and always counted in the run summary. |
| industry | string | – | Matches the whole PKD path, so "SEKCJA K" selects the entire financial sector while "TELEKOMUNIKACJA" selects one class. Because the register stores the path but each decision page shows only the lea… |
| maxItems | integer | – | Optional cap on billed dataset items returned. |
| participant | string | – | Name of a party to the proceedings, e.g. "Orange". Matches whole words in the party field, case-insensitive. Polish diacritics matter - the register's search is literal. |
| practiceType | string | – | The category of proceedings. Roughly: merger control 5,800 decisions, product-safety conformity 4,000, collective consumer interests 4,000, dominant position 1,900. |
| region | string | – | Region the decision applies to. A decision can list several. |
No output schema declared.
No examples provided.
regdata_us_county_recorded_documents ~507
US County Clerk Records - lis pendens, liens and deeds (Texas, Ohio, Michigan and more). Daily index of documents recorded with US county clerks in selected counties across Texas, Ohio, Michigan, Pennsylvania, Colorado and other states (counties enum in the input): lis pendens, liens, deeds, deeds of trust, releases, affidavits of heirship and sheriff's deeds, with recorded date, document category and grantor and grantee names. Use for pre-foreclosure and probate lead lists, lien monitoring on a named party, and title research. Pick counties and a recorded-date window (at most 31 days per run; the newest day can still be incomplete while the county finishes indexing), optionally document categories or a party name (counties index people as LAST FIRST). onlyNewSinceLastRun makes a scheduled run deliver each document once. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).
| Name | Type | Req | Description |
|---|---|---|---|
| counties | array | yes | The counties to read, from the county clerk's official public records search. Counties are read one after another. |
| dateFrom | string | – | First recorded date, YYYY-MM-DD. Default: yesterday. At most 31 days per run. |
| dateTo | string | – | Last recorded date, YYYY-MM-DD, inclusive. Default: yesterday. Counties publish each day once their indexing is done, so the most recent day can still be incomplete. |
| documentCategories | array | – | Keep only these kinds of documents. Leave empty for every document recorded in the window. Each document gets one category, matched on the county's document type wording. |
| maxItems | integer | – | Optional cap on billed dataset items returned. |
| maxResults | integer | – | Most documents delivered in this run, across all counties. 0 = no limit. |
| onlyNewSinceLastRun | boolean | – | For a scheduled daily feed: skips documents this feed already delivered (remembered for 60 days), so a window that overlaps the previous run still delivers each document once. |
| partyName | string | – | Only documents where this name appears as a grantor or grantee, e.g. "SMITH JOHN" or a company name. Counties index people as LAST FIRST. Leave empty for every document in the window. |
| stateStoreName | string | – | Key-value store in your Apify account that remembers delivered documents. Use a different name for each independent feed. |
No output schema declared.
No examples provided.
regdata_wko_business_directory ~359
Austria WKO Business Directory Scraper. Scrape 620,000+ Austrian businesses from WKO Firmen A-Z - the official Chamber of Commerce directory. Get company names, addresses, phone numbers, emails, websites, industry codes, and trade licenses. No API exists for this data. Advanced fields beyond this schema are also accepted (regdata_describe lists them).
| Name | Type | Req | Description |
|---|---|---|---|
| bezirk | string | – | Optional district filter, e.g. 'Linz-Land', 'Hallein', 'Moedling'. For Vienna use a district name or its number ('Innere Stadt', 'Landstrasse', or '3'). Needs a searchQuery alongside it - a district… |
| branche | string | – | Industry or trade classification to search for (e.g., 'IT-Dienstleistung', 'Gastronomie', 'Tischlerei', 'Elektrotechnik'). Synonym of searchQuery and used as the primary search term on firmen.wko.at… |
| bundesland | string | – | Austrian federal state to filter results. Leave empty for all of Austria. |
| maxItems | integer | – | Optional cap on billed dataset items returned. |
| maxResults | integer | – | Maximum number of company records to return. The actor pages through the directory until it reaches this limit or runs out of matches. Default: 100. |
| searchQuery | string | – | Keyword search for company name or service (e.g., 'Software', 'Gastronomie', 'Steuerberater'). Supply this OR bundesland at minimum - 'branche' is an accepted synonym, so filling either one is enough. |
No output schema declared.
No examples provided.
How do I install the io.github.Nolpak14/getregdata MCP server?
io.github.Nolpak14/getregdata runs locally as an npm package, launched with npx -y getregdata-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · getregdata-mcp
claude mcp add nolpak14-getregdata -- npx -y getregdata-mcp
What is the io.github.Nolpak14/getregdata MCP server?
io.github.Nolpak14/getregdata is an MCP server listed in the public MCP registry as io.github.Nolpak14/getregdata. Official registry data for agents: insolvency across Europe, Poland and CEE KYB, UBO, land registers. This page covers its npm package (getregdata-mcp).
Is the io.github.Nolpak14/getregdata MCP server safe to use?
io.github.Nolpak14/getregdata scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.Nolpak14/getregdata MCP server expose?
io.github.Nolpak14/getregdata exposes 47 tools: regdata_catalog, regdata_run_result, regdata_describe, regdata_poland_kyb_check, regdata_adverse_media, and 42 more. Their descriptions and schemas cost roughly 20,181 tokens of context every time the server is loaded.
Is the io.github.Nolpak14/getregdata MCP server still maintained?
io.github.Nolpak14/getregdata 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 io.github.Nolpak14/getregdata MCP server under?
io.github.Nolpak14/getregdata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.Nolpak14/getregdata MCP server?
VerifyMCP ran 16 checks on io.github.Nolpak14/getregdata, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.