# Malaysia Data Engine (remote · mcp.data-pulse.my)

Read-only NPRA pharmaceutical records and pipeline health for Malaysia (5 tools).

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.data-pulse.my`: 76/100 (this document), [markdown](https://verifymcp.io/servers/r3dz4r-malaysia-data-engine/engine.md), [page](https://verifymcp.io/servers/r3dz4r-malaysia-data-engine/engine)

## Channel facts

- Endpoint: `https://mcp.data-pulse.my/engine`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 319 tokens (~53/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http r3dz4r-malaysia-data-engine 'https://mcp.data-pulse.my/engine'
```

### Cursor

```json
{
  "mcpServers": {
    "r3dz4r-malaysia-data-engine": {
      "url": "https://mcp.data-pulse.my/engine"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "r3dz4r-malaysia-data-engine": {
      "type": "http",
      "url": "https://mcp.data-pulse.my/engine"
    }
  }
}
```

### Codex

```toml
[mcp_servers.r3dz4r-malaysia-data-engine]
url = "https://mcp.data-pulse.my/engine"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "r3dz4r-malaysia-data-engine": {
      "type": "remote",
      "url": "https://mcp.data-pulse.my/engine",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add r3dz4r-malaysia-data-engine --url 'https://mcp.data-pulse.my/engine' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  r3dz4r-malaysia-data-engine:
    url: "https://mcp.data-pulse.my/engine"
```

### Netclaw

```json
{
  "McpServers": {
    "r3dz4r-malaysia-data-engine": {
      "Transport": "http",
      "Url": "https://mcp.data-pulse.my/engine"
    }
  }
}
```

### Vellum

```bash
assistant mcp add r3dz4r-malaysia-data-engine -t streamable-http -u 'https://mcp.data-pulse.my/engine'
```

### Other

```json
{
  "mcpServers": {
    "r3dz4r-malaysia-data-engine": {
      "type": "http",
      "url": "https://mcp.data-pulse.my/engine"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 76, 0)

- [functional] Server version: 6822b6f532455492e5efb9d3f99861bf8f26f242 → 425ec2857bd84aac63fda1a17f22e59904178e07

### 2026-09-19 (score 76, +1)

- [functional] Server version: 925d30249106847b6802129855c375c3f60a2e61 → 6822b6f532455492e5efb9d3f99861bf8f26f242

### 2026-09-18 (score 75, 0)

- [functional] Server version: bb31f3e5ad7c59ffd9c6f55bf756a140c809b2b7 → 925d30249106847b6802129855c375c3f60a2e61

### 2026-09-17 (score 75, +1)

- [functional] Server version: a6ce3da8b18d708710adac69bfbfa76a2980c389 → bb31f3e5ad7c59ffd9c6f55bf756a140c809b2b7

### 2026-09-16 (score 74, 0)

- [functional] Server version: e3d853dd9b7563bcff50f7327cd71b6a48e0dbc4 → a6ce3da8b18d708710adac69bfbfa76a2980c389

### 2026-09-15 (score 74, +1)

- [functional] Server version: 0345c3ae10a7bde9fb49b3b86e5ed20397a9ee2e → e3d853dd9b7563bcff50f7327cd71b6a48e0dbc4

### 2026-09-14 (score 73, 0)

- [functional] Server version: 63077ca0a46e7401f30a7aaeab4e90e39782b59f → 0345c3ae10a7bde9fb49b3b86e5ed20397a9ee2e

### 2026-09-13 (score 73, +1)

- [functional] Server version: 813d9c939ff60d184367416f8661bd089a5083cb → 63077ca0a46e7401f30a7aaeab4e90e39782b59f

## MCP tools (6)

### `search_pharma` (~68 tokens)

Search Pharma

Search one NPRA category by its public searchable fields.

Input parameters:

- `category` (string): NPRA category to search. Defaults to products.
- `limit` (integer): Maximum number of matching products to return. Default 20.
- `q` (string, required): Case-insensitive substring to search for.

### `get_npra_record` (~68 tokens)

Get Npra Record

Return one exact NPRA record, searching all categories by default.

Input parameters:

- `category`: Filter the lookup to one NPRA category; defaults to searching all categories.
- `reg_no` (string, required): Exact NPRA registration number to look up (e.g. MAL16100027TCR).

### `find_recent_changes` (~57 tokens)

Find Recent Changes

Return deduplicated changes from the dated pipeline delta artefacts.

Input parameters:

- `category`: Filter changes to one category; all categories by default.
- `window_days` (integer): Number of days back to include registry changes. Default 7.

### `get_pharma_health` (~20 tokens)

Get Pharma Health

Return the pipeline-produced pharma health document verbatim.

### `find_by_manufacturer` (~40 tokens)

Find By Manufacturer

Find products and related NPRA records for a manufacturer-name substring.

Input parameters:

- `name` (string, required): Manufacturer-name substring to search for (case-insensitive).

### `verify_pharma_artifact` (~48 tokens)

Verify Pharma Artifact

Verify the current canonical pharma graph's local Sigstore DSSE bundle.

Input parameters:

- `include_proof_steps` (boolean): Include capped output from the offline cosign verification command. Default false.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/r3dz4r-malaysia-data-engine/engine#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 67

## Common questions

### 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 76 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?

No. We connected to Malaysia Data Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.data-pulse.my/engine
- Repository: https://github.com/r3dz4r/malaysia-data-engine
- Website: https://www.data-pulse.my/
- Changelog RSS feed: https://verifymcp.io/servers/r3dz4r-malaysia-data-engine/engine.xml
- Changelog JSON feed: https://verifymcp.io/servers/r3dz4r-malaysia-data-engine/engine.json
- HTML version of this page: https://verifymcp.io/servers/r3dz4r-malaysia-data-engine/engine