hk-misc-mcp-server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hk-misc-mcp-serverGet the latest auction data for confiscated and surplus items"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hong Kong Government Data MCP Server
This is an MCP server that provides access to various Hong Kong government data through a FastMCP interface.
Features
Government Auction Data
Get auction data of confiscated, used/surplus, and unclaimed stores from Government Logistics Department
Related MCP server: Hong Kong Commerce MCP Server
Data Source
Auction data from Government Logistics Department
Examples
Get latest auction data for confiscated and surplus items in Hong Kong
Setup
Clone this repository
Install Python dependencies:
pip install -r requirements.txtRun the server:
python server.py
Running Options
Default stdio mode:
python server.pySSE mode (port 8000):
python server.py --sse
Cline Integration
To connect this MCP server to Cline using stdio:
Add this configuration to your Cline MCP settings (cline_mcp_settings.json):
{
"hk-misc": {
"disabled": false,
"timeout": 3,
"type": "stdio",
"command": "uvx",
"args": [
"hkopenai.hk-misc-mcp-server"
]
}
}Testing
Tests are available in the tests/ directory. Run with:
pytestAvailable Tools
1 toolget_government_auction_dataC
Auction data of confiscated, used/surplus, and unclaimed stores from Government Logistics Department Hong Kong.
| Name | Required | Description | Default |
|---|---|---|---|
| end_year | Yes | Ending year for the data range. | |
| language | Yes | Language code for the data ('EN', 'TC', 'SC'). | |
| end_month | Yes | Ending month for the data range (1-12). | |
| start_year | Yes | Starting year for the data range. | |
| start_month | Yes | Starting month for the data range (1-12). |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not specify whether the operation is read-only, how results are returned, pagination, or any potential system interactions. The only implied behavior is the 'get' action, but no details are given.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, short sentence that is easy to scan and front-loaded with the primary data source. However, it is a sentence fragment lacking a verb, which slightly reduces structural quality. It remains concise and free of filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the fully described schema and the presence of an output schema, the description adequately identifies the data source and categories. It does not mention the date-range filtering or language options, but these are covered in the schema. Overall, it is functional but not particularly rich in context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides full descriptions for all five parameters, so the description does not need to elaborate on them. The description adds no extra semantic context beyond the schema, warranting the baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies the exact data source (Government Logistics Department Hong Kong) and types (confiscated, used/surplus, unclaimed stores), making the tool's focus clear. However, it is a noun phrase rather than a verb phrase, so it relies on the tool name to convey the action of 'get'. It does not explicitly state 'retrieves' or 'lists'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool, no mention of alternatives, prerequisites, or scheduling. The description only states what data is included, leaving the agent to infer usage context from the name and schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v0.1.8- First observed
get_government_auction_data
TDQS
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly and specifically described as retrieving Hong Kong government auction data.
The single tool name follows a clear verb_noun pattern (get_government_auction_data), which is consistent and descriptive. There are no other tools to introduce inconsistency.
The server has only one tool, which is too few for the apparent scope implied by the name 'hk-misc-mcp-server'. A miscellaneous Hong Kong data server would be expected to offer multiple tools covering various datasets, making the current single-tool count inadequate.
The server covers only auction data, leaving many other likely Hong Kong government datasets unaddressed. Even within auction data, there are likely gaps such as filtering, searching, or viewing individual auction details. The overall surface is severely incomplete for the implied miscellaneous data server purpose.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
GSA Auctions API MCP — US federal government surplus auctions (keyed).
Hong Kong Census and Statistics Department (C&SD) open-data MCP.
Government Auctions MCP — physical-asset auctions (surplus, seized, forfeited,
Chile Government Procurement MCP — Mercado Público / ChileCompra (keyless-ish).
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that provides access to Hong Kong government city data, including ambulance service indicators, via a FastMCP interface.2MIT
- AlicenseNot gradedqualityDmaintenanceProvides access to hotel room occupancy rate data in Hong Kong through a FastMCP interface.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides access to Hong Kong food data, including wholesale food prices, through a FastMCP interface.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides access to government development, geography and land information data through a FastMCP interface, including data on new building plans processed by the Building Authority.1MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hkopenai/hk-misc-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server