datapulse-my
Related Servers
Alternatives to datapulse-my
- AlicenseAqualityDmaintenanceProvides seamless access to Malaysia's official government data catalogue, enabling developers to discover, explore, and fetch datasets from the Malaysian government's open data platform through a simple, unified interface.46 npm12ISC
- AlicenseNot gradedqualityBmaintenanceConnects to Malaysia's OpenDOSM open data API via Pipeworx, enabling access to official statistics through MCP tools or natural language queries.7 npmMIT
- AlicenseAqualityBmaintenanceEnables querying Malaysian official statistics through natural language, with correct series resolution, statistical transformations, and provenance-attached data.11MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables unified search and retrieval across Malaysia's open data catalogue, dashboards, DOSM datasets, weather forecasts and warnings, flood warnings, and GTFS transit routes and stops through keyless MCP tools.MIT
- AlicenseAqualityDmaintenanceModel Context Protocol (MCP) server that provides weather forecast, warnings, water level associated with flood, and earthquake reports from Malaysia Government's Open API.41MIT
- AlicenseNot gradedqualityAmaintenanceProvides access to Indonesian government data sources (BPOM, BPJPH, AHU, etc.) via a unified API and MCP tools.37 PyPI12MIT
- AlicenseNot gradedqualityDmaintenance26 US federal data domains as 23 MCP tools. Ed25519 signed responses. Free, no API key.91 npm1MIT
- AlicenseAqualityDmaintenanceIndependent trust scores, claim audits, and side-by-side comparisons for AI agents, queryable over MCP. Every verdict is backed by hands-on testing and signed evidence from Hlido (hlido.eu). Hosted endpoint available at https://hlido.eu/mcp — no auth required.14MIT
- AlicenseBqualityAmaintenanceProvides source-cited access to official UAE open data through any MCP client, with PII redaction and SSRF protection built in.111MIT
TDQS
Scored across 19 tools
The six find_* tools are cleanly separated by dimension (stale, anomalies, deteriorating, recovering, unreliable, schema drift), and the verify_* triple (published artifacts vs. live transport vs. signature) is well delineated. However, a family of five per-dataset readers—get_dataset, get_data_passport, get_provenance, get_evidence, trust_verdict—all return published artifacts for one dataset, creating real selection risk that only the elaborate cross-referencing in descriptions mitigates.
Most tools follow a clean verb_noun or verb_prep_noun pattern (get_dataset, search_datasets, find_stale, verify_evidence, find_by_licence). The two exceptions—trust_verdict and usage_summary—drop the verb prefix, a minor deviation from an otherwise predictable convention.
19 tools is on the heavy side and sits at the borderline the rubric flags, but the domain (catalogue freshness, provenance, drift, reliability, reconciliation, attestation, analytics) is genuinely broad and each tool maps to a distinct capability. It is slightly over-provisioned rather than padded.
The surface covers the full lifecycle: discovery (search_datasets, find_by_licence), single-dataset detail (get_dataset, get_data_passport), evidence and citation (get_provenance, get_evidence), trust and verification (verify_dataset, verify_evidence, verify_attestation, trust_verdict), risk enumeration (all find_* tools), reconciliation, catalogue summary, and usage analytics. No obvious gaps or dead ends remain.