← Back to directory

Hong Kong Company MCP (86HC)

HC BUSINESS LIMITED · Compliance, Risk & Regulatory

MCP ServerCommunity

Hong Kong Company MCP provides remote Hong Kong company search, company details and filing retrieval through HC BUSINESS LIMITED. Advisory-firm compliance and onboarding teams could use it for company checks during KYC, customer due diligence and source-of-wealth reviews. Its published tools also include paid filing orders, corporate bank-account eligibility screening and bank-account application submission.

hong kongcompany recordskycdue diligencecompany filingsbank onboarding
Status
Community
Auth
None
Hosting
Remote
Community rating
Not rated yet
Role

Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →

Open documentation →

Caveats

  • The vendor reports version 1.3.0, online status and nine tools. Availability, record accuracy and tool behavior have not been independently verified.
  • Vendor-reported guest access requires no API key and permits three free company-detail retrievals per day per IP. An optional free API key advertises a 20-per-day allowance, supported through an X-API-Key header or URL query parameter.
  • Coverage is described as Hong Kong company records, and some retrievals are paid. The submission states that the operator is neither a government Companies Registry site nor a law firm.
  • This is not read-only: vendor-listed tools include creating filing orders, managing account credits and submitting bank-account applications. No securities-trading tools are listed.
  • The vendor describes a remotely hosted service. The supplied material does not specify retention, storage location or handling of company queries and bank-application information.
  • The submission identifies the repository as MIT-licensed; that license has not been independently checked and does not establish that hosted data retrievals are free.
  • Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
Rate this server

How to connect Hong Kong Company MCP (86HC)

Step 1

Remote server: paste a URL

Hong Kong Company MCP (86HC) publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://www.86hc.com/wp-json/hkquery/v1/mcp/rpc

Client config snippet

{
  "mcpServers": {
    "9996c290-55e4-4b9a-9b39-daa3d3076147": {
      "url": "https://www.86hc.com/wp-json/hkquery/v1/mcp/rpc"
    }
  }
}

Step 2

Authenticate with no credentials

No credentials are required for public data. Rate limits still apply, so avoid bulk pulls from a chat client.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Compliance, Risk & Regulatory.

Compliance history and diligence file

The regulatory record a buyer's counsel will request.

Sell / M&A ReadinessCompliance, Risk & RegulatoryAdvisor & Firm Intelligence / Prospecting

Read-only: assemble my firm's regulatory record from two directions, my internal compliance or GRC systems for what they actually hold (policy versions, control testing, vendor diligence, open findings and remediation status) and the public regulatory and firm-intelligence sources for registration history, ADV disclosures and complaints. Show them side by side and flag anything disclosed publicly with no internal record, or internally tracked that the public record does not reflect. List exam findings and correspondence separately as 'to gather offline' unless a connected system genuinely holds them. Cite each source and mark anything unverified as 'to confirm'. Do not file, submit or amend anything.

Guardrail · Read-only. The internal half of this record usually lives outside any connected tool, and filings are amended through official channels only.

Diligence readiness checklist

A gap list before you open a data room.

Sell / M&A ReadinessCRMCompliance, Risk & RegulatoryAccounting & Tax

Build a diligence readiness checklist across client, financial, custody and compliance records. For each item say whether it exists today, where it lives, and what work is needed. Use read-only access, keep client identities out of the output, and do not create or share a data room or upload any document.

Guardrail · Read-only. Never let a tool export client data to an external destination.

Annual compliance review prep

A gap list against your compliance calendar.

Compliance & Audit ReadinessCompliance, Risk & RegulatoryCRM

Read-only: review my annual compliance calendar against what my connected systems can actually evidence. Use the compliance or GRC platform for the items it genuinely holds, such as policy versions, control testing, vendor diligence and open findings, and use CRM for the client-facing items, disclosure delivery, agreement dates, suitability updates and contact records for the sample under review. List Item / Owner / Due / Status / Evidence location / Source tool, and mark any calendar item that no connected system covers as 'no connected source' rather than inferring its status. Do not mark anything complete, edit records or file anything.

Guardrail · Read-only. Most servers in this category cover firm security and GRC rather than adviser books and records, so expect gaps a person has to fill.

Read the full connection guide →