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.

Sk Rpo

NPM · @PIPEWORX/MCP-SK-RPO · 2 COMPONENTS

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

80 Trust /100

Last scanned (10 hours ago)

Scores higher than 65% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sk-rpo). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
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.

  • 5 Nov 26 0
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 4 Nov 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.

  • 2 Nov 26 +2
    • Stability: unverified → 0.10 ▲ functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 77

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-sk-rpo@0.2.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 pipeworx-io/mcp-sk-rpo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-sk-rpo/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3692351931
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ba2d8bc4663d42698768ec67a9438b17eea7dc0d3e5d9c5ae876c8d94f255cc93b67581412f9c60a2d899bb5e627a648aac17131b7e887872f6307515

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~795 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
rpo_entity_detail ~252

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.

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

No output schema declared.

No examples provided.

rpo_search_entity ~543

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.

NameTypeReqDescription
addressMunicipalitystring–Municipality of the registered address, e.g. "Bratislava".
addressStreetstring–Street of the registered address.
establishmentAfterstring–Only entities established on/after this date, YYYY-MM-DD.
establishmentBeforestring–Only entities established on/before this date, YYYY-MM-DD.
fullNamestring–Company/entity name, full or partial, e.g. "ESET" or "Slovak Telekom". Diacritics-insensitive substring match.
identifierstring–IČO — the 8-digit Slovak business identifier, e.g. "31333532". Exact match when 3+ digits.
legalFormstring–Legal form, e.g. "Akciová spoločnosť" (joint-stock), "Spoločnosť s ručením obmedzeným" (s.r.o.).
limitnumber–Max results to return (default 20, max 100). The upstream itself may have already matched more — see `total_returned_by_api`.
onlyActiveboolean–true to exclude terminated/wound-up entities.
stakeholderCompanyNamestring–Find entities where a stakeholder (owner/partner) is a company matching this name.
stakeholderPersonFamilyNamestring–Find entities where a stakeholder (owner/partner) is a person with this family name.
statutoryBodyFamilyNamestring–Find entities where a statutory-body member (director/executive) has this family name.
terminationAfterstring–Only entities terminated/wound up on/after this date, YYYY-MM-DD.
terminationBeforestring–Only entities terminated/wound up on/before this date, YYYY-MM-DD.

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-sk-rpo

# add to Claude Code
claude mcp add pipeworx-io-sk-rpo -- npx -y @pipeworx/mcp-sk-rpo
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.