# Sk Rpo (npm · @pipeworx/mcp-sk-rpo)

RPO — Register právnických osôb, podnikateľov a orgánov verejnej moci (Register of Legal Entities…

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 80/100, [markdown](https://verifymcp.io/servers/pipeworx-io-sk-rpo/sk-rpo-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-sk-rpo/sk-rpo-mcp)
- npm · `@pipeworx/mcp-sk-rpo`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-sk-rpo/pipeworx-mcp-sk-rpo.md), [page](https://verifymcp.io/servers/pipeworx-io-sk-rpo/pipeworx-mcp-sk-rpo)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-sk-rpo`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sk-rpo).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 849 tokens (~424/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Sk Rpo MCP server?

Sk Rpo runs locally as an npm package, launched with npx -y @pipeworx/mcp-sk-rpo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-sk-rpo -- npx -y @pipeworx/mcp-sk-rpo
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-sk-rpo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sk-rpo"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-sk-rpo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sk-rpo"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-sk-rpo -- npx -y @pipeworx/mcp-sk-rpo
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-sk-rpo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-sk-rpo"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-sk-rpo --command npx --arg -y --arg @pipeworx/mcp-sk-rpo
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-sk-rpo:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-sk-rpo"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-sk-rpo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-sk-rpo"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-sk-rpo -t stdio -c npx -a -y @pipeworx/mcp-sk-rpo
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-sk-rpo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sk-rpo"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-04 (score 80, +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.

### 2026-11-02 (score 79, +2)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-31 (score 77, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 77)

First indexed and scored.

## MCP tools (2)

### `rpo_search_entity` (~543 tokens)

Search the Slovak Register of Legal Entities (RPO) for companies, sole traders and public bodies. Matches are a diacritics-insensitive SUBSTRING search (e.g. "s" matches "š"), not relevance-ranked, so a short or common query can return hundreds of unrelated hits — use the fullest name you have, or the IČO, for a specific match. Legal-form suffixes (s.r.o., a.s., k.s., etc.) are part of the stored name and can be included or omitted. At least one filter is required. Returns each match's internal `id` (pass to rpo_entity_detail for the full record), current/historical names, IČO, addresses and establishment/termination dates. The upstream caps results at 500; narrow the query if you hit that.

Input parameters:

- `addressMunicipality` (string): Municipality of the registered address, e.g. "Bratislava".
- `addressStreet` (string): Street of the registered address.
- `establishmentAfter` (string): Only entities established on/after this date, YYYY-MM-DD.
- `establishmentBefore` (string): Only entities established on/before this date, YYYY-MM-DD.
- `fullName` (string): Company/entity name, full or partial, e.g. "ESET" or "Slovak Telekom". Diacritics-insensitive substring match.
- `identifier` (string): IČO — the 8-digit Slovak business identifier, e.g. "31333532". Exact match when 3+ digits.
- `legalForm` (string): Legal form, e.g. "Akciová spoločnosť" (joint-stock), "Spoločnosť s ručením obmedzeným" (s.r.o.).
- `limit` (number): Max results to return (default 20, max 100). The upstream itself may have already matched more — see `total_returned_by_api`.
- `onlyActive` (boolean): true to exclude terminated/wound-up entities.
- `stakeholderCompanyName` (string): Find entities where a stakeholder (owner/partner) is a company matching this name.
- `stakeholderPersonFamilyName` (string): Find entities where a stakeholder (owner/partner) is a person with this family name.
- `statutoryBodyFamilyName` (string): Find entities where a statutory-body member (director/executive) has this family name.
- `terminationAfter` (string): Only entities terminated/wound up on/after this date, YYYY-MM-DD.
- `terminationBefore` (string): Only entities terminated/wound up on/before this date, YYYY-MM-DD.

### `rpo_entity_detail` (~252 tokens)

Fetch the full RPO record for one entity: legal forms, registered address history, statutory bodies (directors/executives), stakeholders (owners/partners), equity and shares, predecessors (mergers/splits), statistical classification codes, and the source register (Obchodný register / Živnostenský register / etc.) with registration number. Pass either `id` (the internal RPO id returned by rpo_search_entity) or `ico` (the 8-digit IČO) — if you pass `ico`, this tool resolves it to the internal id first via an exact-identifier search.

Input parameters:

- `ico` (string): IČO — the 8-digit Slovak business identifier, e.g. "31333532". Used to look up the entity if `id` is not given.
- `id` (number): Internal RPO entity id, from rpo_search_entity results (the `id` field).
- `includeHistory` (boolean): Include historical (superseded) names, addresses, legal forms etc., not just the current ones. Default true.
- `includeOrganizationUnits` (boolean): Include organizational units (branches) of the entity. Default true.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-sk-rpo/pipeworx-mcp-sk-rpo#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 77

## Common questions

### What is the Sk Rpo MCP server?

Sk Rpo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sk-rpo. RPO, Register právnických osôb, podnikateľov a orgánov verejnej moci (Register of Legal Entities… This page covers its npm package (@pipeworx/mcp-sk-rpo).

### Is the Sk Rpo MCP server safe to use?

Sk Rpo scores 80 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 Sk Rpo MCP server expose?

Sk Rpo exposes 2 tools: rpo_search_entity, rpo_entity_detail. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.

### Is the Sk Rpo MCP server still maintained?

Sk Rpo 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 Sk Rpo MCP server under?

Sk Rpo 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 Sk Rpo MCP server?

VerifyMCP ran 16 checks on Sk Rpo, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-sk-rpo
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-sk-rpo
- Repository: https://github.com/pipeworx-io/mcp-sk-rpo
- Website: https://pipeworx.io/packs/sk-rpo
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-sk-rpo/pipeworx-mcp-sk-rpo.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-sk-rpo/pipeworx-mcp-sk-rpo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-sk-rpo/pipeworx-mcp-sk-rpo.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-sk-rpo/pipeworx-mcp-sk-rpo