Skip to main content
Glama
Sign In

Hong Kong Company Registry & Due Diligence (86hc.com)

by com.86hc
OverviewDiscussionsAdmin

submit_bank_account_application

Submit an online Hong Kong corporate bank account opening pre-screening application (Stage 1 KYC dossier) for HSBC Hong Kong (hsbc) or OCBC Bank Hong Kong (ocbc). REQUIRES USER LOGIN (personal API Key hkq_live_... obtained after signing in at https://www.86hc.com/user, passed via X-API-Key header or api_key parameter). Automatically resolves the company from 86hc.com's 3.9M+ registry, binds the BK-YYYYMMDD-XXXXXX reference number to the user's account, notifies HC Business licensed TCSP (TC006431) compliance officers in real time, sends an official confirmation email, and returns a Stage 2 continuation URL where the logged-in user can upload statutory documents (CI, BRC, NNC1/NAR1, IDs) and complete Cap. 553 electronic signature.

Input Schema

NameRequiredDescriptionDefault
api_keyNoPersonal 86hc.com API Key (hkq_live_xxxx) obtained after signing in at https://www.86hc.com/user (required if X-API-Key header is not configured).
industryNoIndustry sector (e.g. EXPORT_TRADE, ECOMMERCE_2C, ECOMMERCE_2B, IT_SOFTWARE, CONSULTING_SVC, STARTUP_COMPANY, LOGISTICS_SUPPLY).
turnoverNoEstimated annual turnover (UNDER_1M, 1M_TO_3M, 3M_TO_5M, 5M_TO_10M, OVER_10M).
user_noteNoOptional additional notes or questions from the applicant.
currenciesNoRequired settlement currencies (e.g. ["USD", "HKD", "CNH", "EUR", "SGD"]).
identifierYesHong Kong company name (Chinese or English), 7-digit CR number, or 8-digit BRN.
bank_targetNoTarget bank: hsbc (HSBC Hong Kong), ocbc (OCBC Bank Hong Kong), or both.hsbc
top_clientsNoOptional names of top 1-5 customers/buyers.
contact_nameYesFull name of the applicant / director / authorized handler.
contact_emailNoApplicant email address to receive the official application receipt and compliance review updates.
contact_phoneYesContact mobile phone number with country/region code (e.g. +86 13800138000 or +852 91234567).
top_suppliersNoOptional names of top 1-5 suppliers/vendors.
agent_platformNoOptional name of the calling AI platform (e.g. ChatGPT, Claude, Coze, Doubao, Baidu Wenxin).
applicant_roleNoRole of the applicant in the Hong Kong company.SHAREHOLDER_DIR
contact_wechatNoOptional WeChat ID or WhatsApp number for 1-on-1 compliance officer liaison.
signing_locationNoPreferred signing mode (e.g. 赴港分行现场面签 or 内地指定城市分行视频见证).
products_servicesNoSpecific goods traded or services rendered (e.g. Consumer electronics export, cross-border SaaS subscription).
trading_countriesNoMajor counterparty countries or regions (e.g. ["China", "Hong Kong", "Singapore", "USA"]).
has_mainland_companyNoWhether there is an affiliated Mainland China operating company.
mainland_company_nameNoOptional name of the affiliated Mainland China company.
directors_shareholdersNoOptional summary of directors and 25%+ Ultimate Beneficial Owners (UBO).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
+  "description": "Personal 86hc.com API Key (hkq_live_xxxx) obtained after signing in at https://www.86hc.com/user (required if X-API-Key header is not configured).",
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare it is a non-read-only, non-idempotent write; the description goes far beyond that by disclosing the auth requirement (hkq_live key via header or parameter), the real-time side effects (registry company resolution, binding a BK-YYYYMMDD-XXXXXX reference to the account, TCSP compliance officer notification, confirmation email), and the Stage 2 continuation URL returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded paragraph that leads with the action and resource before the prerequisites and effects. It is dense and mostly earns its length, though marketing-flavored details ('3.9M+ registry', the TCSP licence number) are closer to persuasion than agent guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 21-parameter mutation with no output schema, the description covers the essentials: authentication, what is created, the reference number, the follow-up artifacts, and the next-stage handoff. Combined with 100% schema coverage, an agent has what it needs to invoke this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics the schema does not: the identifier is automatically resolved against an external company registry (so a name, CR, or BRN are all acceptable) and bank_target drives which institution(s) receive the dossier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Submit an online Hong Kong corporate bank account opening pre-screening application'), scopes it to Stage 1 KYC, names the two supported banks, and thereby separates it from siblings like create_filing_order or assess_bank_account_eligibility.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The login prerequisite and the Stage 1 → Stage 2 progression imply when this applies, but the description never states when to choose it over assess_bank_account_eligibility or check_bank_application_status, nor what to do if eligibility hasn't been assessed. Usage is inferable but not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hong Kong Company Registry & Due Diligence (86hc.com) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources