Skip to content
MCPSTAMP
MCP server report

Hongkong company MCP server

com.86hc/hongkong-company

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 89 of 100 (grade B), higher than 60.6% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, ChatGPT and MCP Registry. Not ready for Gemini.

Measured facts

Score
89B
Sign-in
No sign-in
Tools listed
9
Protocol version
2026-07-28
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Ready No blocking check failed.
Gemini Connected Apps Not ready Blocked by Supported protocol version negotiated.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    Supported protocol version negotiated

    protocol_version

    Blocks Gemini.

    Measured Negotiated 2026-07-28, newer than the 2025-11-25 the client asked for

    When the client asks for 2025-11-25, answer with 2025-11-25. Gemini Connected Apps supports versions up to 2025-11-25 only.

  2. Fails

    GET answers SSE or 405

    get_stream

    Measured HTTP 200 application/json

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

  3. Warning

    initialize latency

    latency

    Measured 2084 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

14 checks passed, 10 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, JSON or SSE response Content-Type, JSON-RPC error for unknown method, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool, Tool descriptions.

Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Hongkong company

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fwww.86hc.com%2Fwp-json%2Fhkquery%2Fv1%2Fmcp%2Frpc)](https://www.mcpstamp.com/r/com-86hc-hongkong-company/)

HTML

<a href="https://www.mcpstamp.com/r/com-86hc-hongkong-company/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fwww.86hc.com%2Fwp-json%2Fhkquery%2Fv1%2Fmcp%2Frpc" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Search 3.9M+ HK companies (CR, BRN, UBO, status) & order NAR1/NNC1 filings via Stripe. Free trial.
Registry name
com.86hc/hongkong-company
Remote URL
https://www.86hc.com/wp-json/hkquery/v1/mcp/rpc
Version
1.2.4
Source
github.com/86hc-compliance/hongkong-company-mcp
Website
www.86hc.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026