# DataPulse MY (remote · mcp.data-pulse.my)

Read-only discovery for 122 Malaysian public datasets with freshness, licence, and provenance.

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-08

## Components

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

## Channel facts

- Endpoint: `https://mcp.data-pulse.my/mcp`
- 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-08-08.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 448 tokens (~64/item across 7 items; 5 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

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

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-08-07 (score 59, +41)

- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.13
- [functional improvement] MCP protocol: unverified → pass
- [functional] The server no longer declares the “experimental” capability

### 2026-08-06 (score 18, −40)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.07 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-08-05 (score 58, +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.

### 2026-08-04 (score 57, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-03 (score 57)

First indexed and scored.

## MCP tools (5)

### `search_datasets` (~127 tokens)

Search DataPulse MY's 122 Malaysian public datasets by natural-language query. Filter by licence (e.g. 'CC BY 4.0', 'Open Government Licence (Malaysia)') or source ('OpenDOSM', 'data.gov.my', 'MET Malaysia', etc.). Returns ranked matches: id, title, source, licence, status, score. Use when an agent needs to find datasets covering a topic, by an agency, or under a specific licence.

Input parameters:

- `licence`
- `limit` (integer)
- `query` (string, required)
- `source`

Output parameters:

- `result` (array)

### `get_dataset` (~82 tokens)

Return full detail for one dataset id, including its latest health status and last-verified timestamp, content_freshness_date, and freshness_signal_source (last_modified, content_parse, or none). Use to fetch the provenance/citation metadata for a dataset found via search_datasets and distinguish unknown-freshness from proven stale data.

Input parameters:

- `dataset_id` (string, required)

### `find_stale` (~57 tokens)

Return datasets whose status is aging, stale, or degraded, plus datasets missing from the latest health snapshot. Use when an agent needs to know which data has a freshness or schema-validity risk.

Input parameters:

- `max_age_hours` (integer)

Output parameters:

- `result` (array)

### `get_provenance` (~75 tokens)

Return citation-ready provenance metadata for the listed dataset ids: source steward, licence (with URL), source URL, access method (curl/Camofox), last-verified timestamp. Use when an agent needs to cite DataPulse MY data in a response and must include proper attribution and licence.

Input parameters:

- `dataset_ids` (array, required)

Output parameters:

- `result` (array)

### `find_by_licence` (~45 tokens)

Return all datasets with the given licence, summarised. Use to enumerate what's available under a specific licence for compliance/reuse scoping.

Input parameters:

- `licence` (string, required)

## Diagnostics

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

## Score history

- 2026-08-08: 59
- 2026-08-07: 59
- 2026-08-06: 18
- 2026-08-05: 58
- 2026-08-04: 57
- 2026-08-03: 57

## Links

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