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.42 npm12ISC
- AlicenseNot gradedqualityCmaintenanceConnects to Malaysia's OpenDOSM open data API via Pipeworx, enabling access to official statistics through MCP tools or natural language queries.2 npmMIT
- AlicenseAqualityBmaintenanceEnables querying Malaysian official statistics through natural language, with correct series resolution, statistical transformations, and provenance-attached data.11MIT
Related Servers
- 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.21 PyPI8MIT
- AlicenseNot gradedqualityDmaintenance26 US federal data domains as 23 MCP tools. Ed25519 signed responses. Free, no API key.68 npm1MIT
- AlicenseAqualityCmaintenanceIndependent 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
- AlicenseNot gradedqualityAmaintenanceEnables interaction with Singapore public data including datasets, real-time traffic, weather, and geospatial services through MCP.7MIT
TDQS
Scored across 19 tools
The find_* family is clearly distinct, but there is meaningful overlap among get_dataset, get_data_passport, get_provenance, get_evidence, verify_dataset, trust_verdict, and verify_attestation, all of which return related trust/evidence information. The descriptions use explicit 'use X not Y' guidance, yet an agent could still misselect, especially since get_dataset itself mentions provenance/citation metadata.
Names are uniformly lowercase snake_case and mostly follow a verb_noun pattern like search_datasets, find_stale, and verify_evidence. A few names such as usage_summary and trust_verdict are noun-phrase style, but the overall convention is predictable and readable.
With 19 tools, the server sits in the 16-25 range that feels heavy. Many tools are narrowly scoped variants of finding risk signals or verifying evidence, so the surface could plausibly be consolidated without losing much functionality.
For a read-only data-trust server, the surface is remarkably complete: discovery, metadata, freshness summaries, stale/anomaly/trend/reliability/drift detection, reconciliation, provenance, evidence receipts, live verification, attestation, trust verdicts, and licence filtering are all present. No obvious dead ends or missing lifecycle operations for the stated domain.