Malaysia Data Engine
REMOTE · MCP.DATA-PULSE.MY
Read-only NPRA pharmaceutical records and pipeline health for Malaysia (5 tools).
Available components
Last scanned (11 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.77 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 22 Sept 26 0
- Server version: c4badfadb3b5fcf68ce0a94b9faaf5c287a52239 → 139fbde26d229da80e71313c6dd770efcd3592e3 functional
- 21 Sept 26 0
- Server version: 425ec2857bd84aac63fda1a17f22e59904178e07 → c4badfadb3b5fcf68ce0a94b9faaf5c287a52239 functional
- 20 Sept 26 0
- Server version: 6822b6f532455492e5efb9d3f99861bf8f26f242 → 425ec2857bd84aac63fda1a17f22e59904178e07 functional
- 19 Sept 26 0
- Server version: 925d30249106847b6802129855c375c3f60a2e61 → 6822b6f532455492e5efb9d3f99861bf8f26f242 functional
- 18 Sept 26 0
- Server version: bb31f3e5ad7c59ffd9c6f55bf756a140c809b2b7 → 925d30249106847b6802129855c375c3f60a2e61 functional
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 · Probed https://mcp.data-pulse.my/engine
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=data-pulse.my | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 284ddd208f3420b513452f3bd2a55cbe |
| SANs: data-pulse.my, *.data-pulse.my | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.data-pulse.my. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| my. | present | 47187 | 13 | Verified |
| data-pulse.my. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.data-pulse.my/engine | HTTP error | 503 | |
| http (plaintext) | http://mcp.data-pulse.my/engine | Inconclusive | 503 |
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 →
find_by_manufacturer Find By Manufacturer ~40
Find products and related NPRA records for a manufacturer-name substring.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Manufacturer-name substring to search for (case-insensitive). |
Structured output declared, but exposes no named fields.
No examples provided.
find_recent_changes Find Recent Changes ~57
Return deduplicated changes from the dated pipeline delta artefacts.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | Filter changes to one category; all categories by default. |
| window_days | integer | – | Number of days back to include registry changes. Default 7. |
Structured output declared, but exposes no named fields.
No examples provided.
get_npra_record Get Npra Record ~68
Return one exact NPRA record, searching all categories by default.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | Filter the lookup to one NPRA category; defaults to searching all categories. |
| reg_no | string | yes | Exact NPRA registration number to look up (e.g. MAL16100027TCR). |
Structured output declared, but exposes no named fields.
No examples provided.
get_pharma_health Get Pharma Health ~20
Return the pipeline-produced pharma health document verbatim.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_pharma Search Pharma ~68
Search one NPRA category by its public searchable fields.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | NPRA category to search. Defaults to products. |
| limit | integer | – | Maximum number of matching products to return. Default 20. |
| q | string | yes | Case-insensitive substring to search for. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_pharma_artifact Verify Pharma Artifact ~48
Verify the current canonical pharma graph's local Sigstore DSSE bundle.
| Name | Type | Req | Description |
|---|---|---|---|
| include_proof_steps | boolean | – | Include capped output from the offline cosign verification command. Default false. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Malaysia Data Engine MCP server?
Malaysia Data Engine is a hosted endpoint at https://mcp.data-pulse.my/engine, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.data-pulse.my
claude mcp add --transport http r3dz4r-malaysia-data-engine 'https://mcp.data-pulse.my/engine'
What is the Malaysia Data Engine MCP server?
Malaysia Data Engine is an MCP server listed in the public MCP registry as io.github.r3dz4r/malaysia-data-engine. Read-only NPRA pharmaceutical records and pipeline health for Malaysia (5 tools). This page covers its hosted endpoint (https://mcp.data-pulse.my/engine).
Is the Malaysia Data Engine MCP server safe to use?
Malaysia Data Engine scores 18 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 Malaysia Data Engine MCP server expose?
Malaysia Data Engine exposes 6 tools: search_pharma, get_npra_record, find_recent_changes, get_pharma_health, find_by_manufacturer, verify_pharma_artifact. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.
Does the Malaysia Data Engine MCP server require authentication?
Its publisher declares no required credentials for Malaysia Data Engine. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Malaysia Data Engine MCP server still maintained?
Malaysia Data Engine 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.