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.

Malaysia Data Engine

REMOTE · MCP.DATA-PULSE.MY · SCANNED SEP 20

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

+3 this week 76 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 319 tokens (~53/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 current MCP spec version (2026-07-28).Pass
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.

remote · mcp.data-pulse.my

# add to Claude Code
claude mcp add --transport http r3dz4r-malaysia-data-engine 'https://mcp.data-pulse.my/engine'
// .cursor/mcp.json
{
  "mcpServers": {
    "r3dz4r-malaysia-data-engine": {
      "url": "https://mcp.data-pulse.my/engine"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "r3dz4r-malaysia-data-engine": {
      "type": "http",
      "url": "https://mcp.data-pulse.my/engine"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add r3dz4r-malaysia-data-engine --url 'https://mcp.data-pulse.my/engine' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  r3dz4r-malaysia-data-engine:
    url: "https://mcp.data-pulse.my/engine"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "r3dz4r-malaysia-data-engine": {
      "Transport": "http",
      "Url": "https://mcp.data-pulse.my/engine"
    }
  }
}
# add to Vellum
assistant mcp add r3dz4r-malaysia-data-engine -t streamable-http -u 'https://mcp.data-pulse.my/engine'
// mcp.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 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.

  • 20 Sept 26 0
    • Server version: 6822b6f532455492e5efb9d3f99861bf8f26f242 → 425ec2857bd84aac63fda1a17f22e59904178e07 functional
  • 19 Sept 26 +1
    • Server version: 925d30249106847b6802129855c375c3f60a2e61 → 6822b6f532455492e5efb9d3f99861bf8f26f242 functional
  • 18 Sept 26 0
    • Server version: bb31f3e5ad7c59ffd9c6f55bf756a140c809b2b7 → 925d30249106847b6802129855c375c3f60a2e61 functional
  • 17 Sept 26 +1
    • Server version: a6ce3da8b18d708710adac69bfbfa76a2980c389 → bb31f3e5ad7c59ffd9c6f55bf756a140c809b2b7 functional
  • 16 Sept 26 0
    • Server version: e3d853dd9b7563bcff50f7327cd71b6a48e0dbc4 → a6ce3da8b18d708710adac69bfbfa76a2980c389 functional
  • 15 Sept 26 +1
    • Server version: 0345c3ae10a7bde9fb49b3b86e5ed20397a9ee2e → e3d853dd9b7563bcff50f7327cd71b6a48e0dbc4 functional
  • 14 Sept 26 0
    • Server version: 63077ca0a46e7401f30a7aaeab4e90e39782b59f → 0345c3ae10a7bde9fb49b3b86e5ed20397a9ee2e functional
  • 13 Sept 26 +1
    • Server version: 813d9c939ff60d184367416f8661bd089a5083cb → 63077ca0a46e7401f30a7aaeab4e90e39782b59f functional
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 20 Sept 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 2 Aug 2026 31 Oct 2026 ECDSA 256 ECDSA-SHA256 89a518d1c4182e0e74f90ac74985ec
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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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 Verified 200
http (plaintext) http://mcp.data-pulse.my/engine Inconclusive 405
MCP tools · 6 exposed · ~301 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
find_by_manufacturer ~40

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

NameTypeReqDescription
namestringyesManufacturer-name substring to search for (case-insensitive).

Structured output declared, but exposes no named fields.

No examples provided.

find_recent_changes ~57

Return deduplicated changes from the dated pipeline delta artefacts.

NameTypeReqDescription
categoryFilter changes to one category; all categories by default.
window_daysintegerNumber of days back to include registry changes. Default 7.

Structured output declared, but exposes no named fields.

No examples provided.

get_npra_record ~68

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

NameTypeReqDescription
categoryFilter the lookup to one NPRA category; defaults to searching all categories.
reg_nostringyesExact NPRA registration number to look up (e.g. MAL16100027TCR).

Structured output declared, but exposes no named fields.

No examples provided.

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 ~68

Search one NPRA category by its public searchable fields.

NameTypeReqDescription
categorystringNPRA category to search. Defaults to products.
limitintegerMaximum number of matching products to return. Default 20.
qstringyesCase-insensitive substring to search for.

Structured output declared, but exposes no named fields.

No examples provided.

verify_pharma_artifact ~48

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

NameTypeReqDescription
include_proof_stepsbooleanInclude capped output from the offline cosign verification command. Default false.

Structured output declared, but exposes no named fields.

No examples provided.

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.