Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Macau Stats

NPM · @PIPEWORX/MCP-MACAU-STATS · 2 COMPONENTS

Macau Statistics MCP — DSEC (Direcção dos Serviços de Estatística e Censos 澳門統計暨普查局 / Serviços de…

+4 this week 84 Trust /100

Last scanned (10 hours ago)

Scores higher than 81% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-macau-stats). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 761 tokens (~126/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-macau-stats@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-macau-stats
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-macau-stats/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3649749170
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1ebd1d81438ac85bf7934201a3efad688eddef8dbc55b4d8c7904d884d8e270020d30ef7476c7c5f19df45c7ecb16424a6e9be996ac0544f22302e4f7

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~704 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
macau_employment ~68

Macau's labour-market snapshot from DSEC: overall unemployment rate, total employment and overall median monthly employment earnings (each on its own DSEC reporting cycle — unemployment/employment are rolling 3-month, earnings quarterly). Answers "what is Macau's unemployment rate", "Macau employment statistics".

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

macau_gaming_revenue ~104

Macau's monthly gross revenue of games of chance (澳門博彩毛收入 / receita bruta dos jogos de fortuna ou azar) — the headline casino-gaming-revenue figure, in million MOP, from DSEC. This is the SAME monthly number the gaming regulator DICJ publishes as an HTML table, sourced here as clean structured data. Answers "what was Macau's gaming revenue in August 2026", "Macau casino revenue this month".

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

macau_indicator ~267

Latest published value (and, when a reliable match exists, recent history) for one of Macau's 143 DSEC key indicators. Pass either the numeric `id` from `macau_indicators`, or a `name` keyword (English, 中文 or Portuguese, e.g. "gross revenue of games of chance", "population", "turismo"). Always returns the current value with its reference period and unit; `periods` (default 24) additionally attempts a historical series by matching the indicator against DSEC's general statistics database — this succeeds for many series but not all (some key indicators, notably gaming revenue, exist only as a curated latest-value widget with no general-catalog counterpart), in which case `history` is null and `history_note` explains why. Sourced from DSEC's public TimeSeriesDatabase.asmx web service.

NameTypeReqDescription
idnumber–Numeric KeyIndicatorID from macau_indicators, e.g. 15 for "Gross revenue of games of chance".
namestring–Indicator name or keyword, English/中文/Portuguese, e.g. "gaming revenue", "population".
periodsnumber–How many historical periods to attempt to fetch when a general-catalog match is found (default 24).

No output schema declared.

No examples provided.

macau_indicators ~169

Catalogue of Macau's 143 official key statistical indicators (population, visitor arrivals, gaming revenue, CPI, unemployment, crime, births/deaths, and more) from DSEC (Macao Statistics and Census Service / 澳門統計暨普查局). Returns each indicator's id, name in English, 中文 (Traditional Chinese) and Portuguese, and reporting frequency. Pass `query` to filter by keyword (matches any language); omit it to list all 143. Use this to find the right id/name for `macau_indicator`. Answers "what economic indicators does Macau publish", "find Macau's tourism statistics".

NameTypeReqDescription
querystring–Optional keyword to filter indicators by name, in English, 中文 or Portuguese, e.g. "gaming", "population", "turismo".

No output schema declared.

No examples provided.

macau_population ~39

Macau's total resident population (澳門總人口 / população total de Macau), quarterly, from DSEC. Answers "what is Macau's population".

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

macau_tourism ~57

Macau visitor arrivals (訪澳旅客人數 / chegadas de visitantes a Macau), monthly, from DSEC — the headline tourism-volume figure. Answers "how many tourists visited Macau", "Macau visitor arrivals this month".

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Macau Stats MCP server?

Macau Stats runs locally as an npm package, launched with npx -y @pipeworx/mcp-macau-stats. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-macau-stats

# add to Claude Code
claude mcp add pipeworx-io-macau-stats -- npx -y @pipeworx/mcp-macau-stats
Common questions

What is the Macau Stats MCP server?

Macau Stats is an MCP server listed in the public MCP registry as io.github.pipeworx-io/macau-stats. Macau Statistics MCP, DSEC (Direcção dos Serviços de Estatística e Censos 澳門統計暨普查局 / Serviços de… This page covers its npm package (@pipeworx/mcp-macau-stats).

Is the Macau Stats MCP server safe to use?

Macau Stats scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Macau Stats MCP server expose?

Macau Stats exposes 6 tools: macau_indicators, macau_indicator, macau_gaming_revenue, macau_population, macau_tourism, macau_employment. Their descriptions and schemas cost roughly 704 tokens of context every time the server is loaded.

Is the Macau Stats MCP server still maintained?

Macau Stats is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Macau Stats MCP server under?

Macau Stats declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Macau Stats MCP server?

VerifyMCP ran 16 checks on Macau Stats, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.