Hong Kong Monetary Authority (HKMA) public open API MCP. Keyless.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 36 tools
Several tools have genuinely overlapping boundaries: ask_pipeworx, ask_pipeworx_beta (explicitly stated to currently behave identically), and ask_pipeworx_grounded are three near-identical routers, and ai_visibility_check vs scan_competitor_ai_presence (which wraps the former) also overlap. The descriptions are exceptionally long and do a lot of work to steer selection, and most other groups (memory, subscriptions, polymarket) are clearly distinct, but the router cluster remains a real source of misselection.
Names are overwhelmingly snake_case with sensible domain prefixes (hkma_*, polymarket_*, ask_pipeworx_*), giving a predictable pattern. Minor deviations exist — bare verbs like remember/recall/forget/subscribe/unsubscribe alongside verb_noun and noun-phrase forms (entity_profile, recent_changes) — but nothing chaotic.
36 tools is heavy, and the mismatch is stark: the server is named 'Hkma Hk' yet only 5 tools are HKMA-specific while 31 belong to a general Pipeworx data platform spanning routing, entity research, memory, subscriptions, and Polymarket betting. The breadth means individual tools are defensible, but the count and the name/scope mismatch indicate an over-packed surface.
Core lifecycle coverage is strong: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list_subscriptions/recent_alerts, and HKMA has both a generic dataset fetcher and convenience series tools, with rich research and Polymarket surfaces. Gaps are minor (e.g. no explicit update for stored memory, limited non-HKMA regional data), but no obvious dead ends for the stated purpose.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."Bank Negara Malaysia (BNM) Open API MCP. Keyless.
South African Reserve Bank (SARB) Web API MCP. Keyless.
Bank of Israel public API MCP. Keyless.
Add one secure layer between your agents and this server.