Home / MCP registry index / io.github.r3dz4r/datapulse-my
DataPulse
io.github.r3dz4r/datapulse-my in the official MCP registry.
Endpoint https://mcp.data-pulse.my/mcp. Source: github.com/r3dz4r/datapulse-my.
The registry describes it as: Read-only discovery for 440 Malaysian public datasets with freshness, licence, and provenance.
We read its 19 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_datasets get_dataset get_data_passport find_stale find_anomalies find_deteriorating find_recovering find_unreliable find_schema_drift check_reconciliation get_provenance get_evidence verify_dataset get_freshness_summary verify_evidence trust_verdict verify_attestation find_by_licence usage_summary
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-r3dz4r-datapulse-my)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.