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.

Opendosm My

NPM · @PIPEWORX/MCP-OPENDOSM-MY · 2 COMPONENTS

data.gov.my / OpenDOSM (Department of Statistics Malaysia) — official Malaysian open-data API.…

+3 this week 82 Trust /100

Last scanned (10 hours ago)

Scores higher than 72% 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-opendosm-my). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 788 tokens (~262/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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 +16
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 3 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 79

    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-opendosm-my@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-opendosm-my
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-opendosm-my/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3685077277
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:766114dfb1c74a79f8ca8f101d057d8466a6aced67cf65b67e2d5d00db4cef66343bc0e6a2ec6667e2514a8d543481a5e6049a6189bcaa2ead91f27fe

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 · 3 exposed · ~732 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
opendosm_dataset_meta ~89

Metadata for one Malaysian dataset (data.gov.my): catalogue_id, data_as_of, last_updated, next_update, data_source, update_frequency, plus a sample row showing the available columns. Use this to inspect a series before pulling it, or to check freshness. Requires a dataset id.

NameTypeReqDescription
idstringyesDataset id, e.g. "cpi_headline". Required.

No output schema declared.

No examples provided.

opendosm_get_dataset ~514

Fetch records from an official Malaysian statistics dataset (data.gov.my / OpenDOSM, Dept of Statistics Malaysia). Keyless, authoritative. The dataset `id` is REQUIRED — there is no listing endpoint, so use opendosm_list_datasets or opendosm_dataset_meta to discover ids and their columns. Verified high-value ids: cpi_headline (Headline Consumer Price Index, monthly (1980–present).); cpi_core (Core CPI (excludes volatile items), monthly.); gdp_qtr_real (Real GDP, quarterly (constant 2015 prices).); economic_indicators (Leading / coincident / lagging economic indicator indices, monthly.); ipi (Industrial Production Index, monthly (seasonally adjusted + absolute).); lfs_month (Labour force survey, monthly: unemployment rate, participation rate, employment.); fuelprice (Weekly retail fuel prices (RON95, RON97, diesel) in MYR per litre.); hh_income (Household income: mean and median (MYR), by survey year.); population_malaysia (Malaysia population by age / sex / ethnicity (thousands), annual.); population_state (Population by state, age, sex, ethnicity (thousands).); births (Live births by state and date.); deaths (Deaths: absolute count and crude rate, annual.). Filter syntax is value@column (e.g. filter="overall@division" keeps only rows where division=overall). Range syntax is column[start:end] on NUMERIC columns only, either bound optional (e.g. range="index[130:140]", range="index[135:]"). Date ranges are NOT supported by `range`; instead use sort="-date" with limit to get the most recent rows. sort="-col" is descending, sort="col" ascending.

NameTypeReqDescription
filterstring–Exact-match filter, format value@column, e.g. "overall@division".
idstringyesDataset id, e.g. "cpi_headline", "lfs_month", "fuelprice". Required.
limitinteger–Max records to return. Omit for full series (can be large).
rangestring–Numeric range, format column[start:end] (bounds optional), e.g. "index[130:140]". Numeric columns only — not dates.
sortstring–Sort column; prefix "-" for descending, e.g. "-date" for newest first.

No output schema declared.

No examples provided.

opendosm_list_datasets ~129

List the curated, verified high-value datasets available from data.gov.my / OpenDOSM (Dept of Statistics Malaysia). data.gov.my exposes no machine listing/search endpoint, so this returns a hand-verified set covering inflation, GDP, labour, prices, income, population and demography, with each dataset id, topic, description and its value columns. Optionally filter by topic.

NameTypeReqDescription
topicstring–Optional topic filter, e.g. "inflation", "labour", "population", "gdp", "prices", "income", "demography", "industry".

No output schema declared.

No examples provided.

Install

How do I install the Opendosm My MCP server?

Opendosm My runs locally as an npm package, launched with npx -y @pipeworx/mcp-opendosm-my. 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-opendosm-my

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

What is the Opendosm My MCP server?

Opendosm My is an MCP server listed in the public MCP registry as io.github.pipeworx-io/opendosm-my. data.gov.my / OpenDOSM (Department of Statistics Malaysia), official Malaysian open-data API.… This page covers its npm package (@pipeworx/mcp-opendosm-my).

Is the Opendosm My MCP server safe to use?

Opendosm My scores 82 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 Opendosm My MCP server expose?

Opendosm My exposes 3 tools: opendosm_get_dataset, opendosm_dataset_meta, opendosm_list_datasets. Their descriptions and schemas cost roughly 732 tokens of context every time the server is loaded.

Is the Opendosm My MCP server still maintained?

Opendosm My 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 Opendosm My MCP server under?

Opendosm My 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 Opendosm My MCP server?

VerifyMCP ran 16 checks on Opendosm My, 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.