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.

Hk Companies

NPM · @PIPEWORX/MCP-HK-COMPANIES · 2 COMPONENTS

Hong Kong Companies Registry (香港公司註冊處) open data via data.gov.hk (keyless): search companies by…

+3 this week 89 Trust /100

Last scanned (3 hours ago)

Scores higher than 83% of npm servers

Category Finance and Payments

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-hk-companies). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 20 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1160 tokens (~290/item across 4 items; 4 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 Management80
  • Stability observed for 24 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 (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 →

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.

  • 22 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 21 Nov 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 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.

  • 10 Nov 26 +1

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

  • 8 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.

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

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 · 4 exposed · ~1,105 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
hk_company ~267

Look up a single Hong Kong company by its exact Business Registration (BR) number in the Companies Registry's open incorporation/name-change feed (data.gov.hk, weekly, since 2024-12-30). Returns every appearance of that BR number in the feed — its initial incorporation/registration and any later name change — with the English/Chinese name at each point, company type, and the matching HKEX ticker if it resolves to a listed stock. Returns found:false if the BR number never appears in the feed, which most often means the company pre-dates 2024-12-30 (nothing was wrong — the feed genuinely has no earlier data) or the number is not a real HK BR number. DOES NOT return registered address or company status — Hong Kong has no open API for those (香港公司註冊地址 is not published as open data; the Companies Registry's paid Cyber Search Centre is the only source).

NameTypeReqDescription
brnstringyesExact Business Registration (BR) number, e.g. "81129706".
sincestring–Search back only to this date (YYYY-MM-DD) instead of the default 12-week lookback. Use 2024-12-30 to search the entire feed (fetches more weeks, slower).

No output schema declared.

No examples provided.

hk_company_name_changes ~192

Hong Kong companies that changed their registered name, per the Companies Registry's weekly open-data feed (data.gov.hk, 公司名稱變更, since 2024-12-30). Returns each company's BR number, current English/Chinese name, and the date of the name change, most recent first. The feed has roughly a 1-week publication lag, so a `since` newer than the latest published week returns zero rows with a `data_lag_note` explaining it — that is lag, not "no name changes". Use for "Hong Kong companies that changed their name since <date>", "HK company renames this month".

NameTypeReqDescription
limitnumber|string–Max name changes to return, 1-200 (default 50).
sincestring–Only include name changes on/after this date (YYYY-MM-DD). Default: 7 days before the latest published week.

No output schema declared.

No examples provided.

hk_company_search ~402

Search Hong Kong companies newly incorporated, registered, or renamed on the Companies Registry (香港公司註冊處, cr.gov.hk) since 30 Dec 2024 — official open data via data.gov.hk, updated weekly. Match by company name (English or Chinese, substring, case-insensitive) or an exact Business Registration (BR) number. Returns each match's BR number, English and Chinese name, company type (Hong Kong local / non-Hong Kong), incorporation-or-registration date, and any name-change date, plus the matching HKEX ticker when the name resolves to a listed stock (joined via the same Yahoo Finance lookup hk_resolve_symbol uses — only attached on a confident name match, never guessed). LIMITATION: this only covers companies newly incorporated, registered, or renamed since 2024-12-30 — it is NOT the full historical company register and does NOT return registered address or company status for companies outside that window (Hong Kong publishes no open API for those; only the Companies Registry's paid Cyber Search Centre does). Use for "is there a new HK company called X", "HK BR number for Y", "香港新註冊公司 X".

NameTypeReqDescription
brnstring–Exact Business Registration (BR) number, e.g. "81129706".
limitnumber|string–Max matches to return, 1-100 (default 25).
namestring–Company name substring, English or Chinese, e.g. "HSBC" or "滙豐". Case-insensitive.
sincestring–Only search weeks on/after this date (YYYY-MM-DD). Default: last 12 weeks. Earliest possible: 2024-12-30 (the dataset start).
typestring–Restrict to Hong Kong local companies ("local") or non-Hong Kong companies registered in HK ("non_hk"). Omit to search both.

No output schema declared.

No examples provided.

hk_new_companies ~244

Companies newly incorporated (Hong Kong local) or newly registered/re-domiciled (non-Hong Kong) on the Companies Registry since a given date — the official weekly open-data feed via data.gov.hk (新註冊/新成立公司, since 2024-12-30). Returns each company's BR number, English/Chinese name, type, and incorporation-or-registration date, most recent first. The feed has roughly a 1-week publication lag, so a `since` newer than the latest published week returns zero rows with a `data_lag_note` explaining it — that is lag, not "no new companies". Use for "new Hong Kong companies this week", "companies incorporated in HK since <date>".

NameTypeReqDescription
limitnumber|string–Max companies to return, 1-200 (default 50).
sincestring–Only include companies incorporated/registered on/after this date (YYYY-MM-DD). Default: 7 days before the latest published week.
typestring–Restrict to Hong Kong local companies ("local") or non-Hong Kong companies ("non_hk"). Omit for both.

No output schema declared.

No examples provided.

Install

How do I install the Hk Companies MCP server?

Hk Companies runs locally as an npm package, launched with npx -y @pipeworx/mcp-hk-companies. 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-hk-companies

# add to Claude Code
claude mcp add pipeworx-io-hk-companies -- npx -y @pipeworx/mcp-hk-companies
Common questions

What is the Hk Companies MCP server?

Hk Companies is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hk-companies. Hong Kong Companies Registry (香港公司註冊處) open data via data.gov.hk (keyless): search companies by… This page covers its npm package (@pipeworx/mcp-hk-companies).

Is the Hk Companies MCP server safe to use?

Hk Companies scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Hk Companies MCP server expose?

Hk Companies exposes 4 tools: hk_company_search, hk_company, hk_new_companies, hk_company_name_changes. Their descriptions and schemas cost roughly 1,105 tokens of context every time the server is loaded.

Is the Hk Companies MCP server still maintained?

Hk Companies is still listed as active in the MCP registry. We last reached this channel on 22 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 Hk Companies MCP server under?

Hk Companies 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 Hk Companies MCP server?

VerifyMCP ran 16 checks on Hk Companies, 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.