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.

io.github.CloudCorpRecords/myopendata

OCI · GHCR.IO/CLOUDCORPRECORDS/MYOPENDATA · 2 COMPONENTS

Malaysia open data: datasets, dashboards, DOSM, weather, floods and transit, keyless.

40 Trust /100

Last scanned (5 hours ago)

Scores higher than 41% of OCI 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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 507 tokens (~31/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 4 Nov 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.

  • 2 Nov 26 39

    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 oci/ghcr.io/cloudcorprecords/myopendata@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 16 exposed · ~507 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
get_dashboard_details ~26

Get details for one dashboard by name.

NameTypeReqDescription
namestringyesDashboard name.

No output schema declared.

No examples provided.

get_dataset_details ~29

Get details for one dataset by its catalogue id.

NameTypeReqDescription
idstringyesDataset catalogue identifier.

No output schema declared.

No examples provided.

get_dosm_dataset ~29

Get one DOSM dataset by id.

NameTypeReqDescription
idstringyesDOSM dataset identifier.

No output schema declared.

No examples provided.

get_flood_warnings ~16

Get current flood warnings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_transit_routes ~46

Get transit routes for a GTFS provider, optionally by category.

NameTypeReqDescription
categorystring–Transit category to filter by.
providerstringyesGTFS provider identifier.

No output schema declared.

No examples provided.

get_transit_stops ~47

Get transit stops for a GTFS provider, optionally by category.

NameTypeReqDescription
categorystring–Transit category to filter by.
providerstringyesGTFS provider identifier.

No output schema declared.

No examples provided.

get_weather_forecast ~33

Get the weather forecast, optionally filtered by location.

NameTypeReqDescription
locationstring–Location to filter the forecast by.

No output schema declared.

No examples provided.

get_weather_warnings ~15

Get current weather warnings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hello ~36

Return a greeting string. Health-check style tool for connectivity testing.

NameTypeReqDescription
namestring–Name to greet; defaults to World if omitted.

No output schema declared.

No examples provided.

list_dashboards ~26

List available dashboards.

NameTypeReqDescription
limitinteger–Maximum number of dashboards to return.

No output schema declared.

No examples provided.

list_datasets_catalogue ~31

List datasets in the data catalogue.

NameTypeReqDescription
limitinteger–Maximum number of datasets to return.

No output schema declared.

No examples provided.

list_dosm_datasets ~35

List Department of Statistics Malaysia (DOSM) datasets.

NameTypeReqDescription
limitinteger–Maximum number of datasets to return.

No output schema declared.

No examples provided.

list_transport_agencies ~18

List transport agencies with GTFS data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_all ~40

Search datasets and dashboards together for a query.

NameTypeReqDescription
limitinteger–Maximum number of results to return.
querystringyesSearch query text.

No output schema declared.

No examples provided.

search_dashboards ~38

Search dashboards for a query.

NameTypeReqDescription
limitinteger–Maximum number of dashboards to return.
querystringyesSearch query text.

No output schema declared.

No examples provided.

search_datasets_catalogue ~42

Search the dataset catalogue for a query.

NameTypeReqDescription
limitinteger–Maximum number of datasets to return.
querystringyesSearch query text.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/myopendata MCP server?

io.github.CloudCorpRecords/myopendata runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/myopendata:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/myopendata

# add to Claude Code
claude mcp add cloudcorprecords-myopendata -- docker run --rm -i ghcr.io/cloudcorprecords/myopendata:0.1.0
Common questions

What is the io.github.CloudCorpRecords/myopendata MCP server?

io.github.CloudCorpRecords/myopendata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/myopendata. Malaysia open data: datasets, dashboards, DOSM, weather, floods and transit, keyless. This page covers its container image (ghcr.io/cloudcorprecords/myopendata).

Is the io.github.CloudCorpRecords/myopendata MCP server safe to use?

io.github.CloudCorpRecords/myopendata scores 40 out of 100 on VerifyMCP. 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 io.github.CloudCorpRecords/myopendata MCP server expose?

io.github.CloudCorpRecords/myopendata exposes 16 tools: search_all, list_datasets_catalogue, search_datasets_catalogue, get_dataset_details, list_dashboards, and 11 more. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/myopendata MCP server still maintained?

io.github.CloudCorpRecords/myopendata 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 io.github.CloudCorpRecords/myopendata MCP server under?

io.github.CloudCorpRecords/myopendata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.