Data.gov.my MCP Server
Related Servers
Alternatives to Data.gov.my MCP Server
No user-submitted related servers found.
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
- AlicenseNot gradedqualityDmaintenanceProvides access to Singapore's data.gov.sg government datasets and collections, enabling search, metadata retrieval, and dataset downloads through the CKAN datastore API.4MIT
- AlicenseAqualityBmaintenanceTrust layer for 412 official Malaysian public datasets, with freshness, licences, and a public read-only MCP server. No API key.8193MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and retrieve datasets, publishers, and themes from Spain's national open-data catalogue through keyless MCP tools or HTTP endpoints.525 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides access to Ontario open government data through the CKAN API, enabling dataset search, organization browsing, and resource data queries.-
- AlicenseAqualityCmaintenanceEnables access to Hong Kong government's official open data portal (DATA.GOV.HK) through natural language queries. Supports searching datasets, browsing categories, and retrieving detailed information about Hong Kong's public data resources.88MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list_catalogue_ids enumerates available IDs, get_catalogue_metadata retrieves metadata for a specific ID, get_catalogue_data fetches actual data for a catalogue, and search_catalogues performs keyword searches. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_catalogue_data, list_catalogue_ids). The verbs (get, list, search) are appropriately chosen and consistently applied, making the naming predictable and readable.
With 4 tools, this server is well-scoped for its purpose of interacting with data catalogues. Each tool serves a distinct and necessary function, and the count is neither too sparse nor excessive, fitting typical expectations for a focused API client.
The toolset covers core operations for browsing and retrieving catalogue information (list, search, get metadata, get data), providing a solid foundation. A minor gap exists in lacking update or management operations, but this is reasonable for a read-only data access server, and agents can work effectively with the available tools.