`hk_company_name_changes`

Pack: hk-companies · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/hk_company_name_changes for the schema, then POST the same URL with its arguments for the data.

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 ”, “HK company renames this month”.

Parameters

Name	Type	Required	Description
`since`	string	no	Only include name changes on/after this date (YYYY-MM-DD). Default: 7 days before the latest published week.
`limit`	number,string	no	Max name changes to return, 1-200 (default 50).

Example call

Arguments

{
  "since": "2026-08-17"
}

curl

curl -X POST https://gateway.pipeworx.io/hk-companies/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"hk_company_name_changes","arguments":{"since":"2026-08-17"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('hk_company_name_changes', {
  "since": "2026-08-17"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the hk-companies pack

{
  "mcpServers": {
    "hk-companies": {
      "url": "https://gateway.pipeworx.io/hk-companies/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

hk_company_name_changes