MLIT Data Platform MCP Server
Related Servers
Alternatives to MLIT Data Platform MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables LLMs to search and retrieve Japanese real estate data through unified access to the MLIT Real Estate Information Library API, supporting over 25 geospatial datasets for interactive queries.189MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the MLIT Data Platform that enables natural language search and retrieval of Japanese government infrastructure and transport data.171MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query Japanese public data (laws, corporations, statistics) from official government APIs, returning normalized English metadata with source attribution.1MIT
- AlicenseAqualityCmaintenanceEnables querying Utsunomiya city's open datasets using natural language, with features like listing datasets, viewing schemas, filtering, and statistical analysis.5MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to access and compare Japanese public data from e-Stat, corporate registration, real estate, and invoice APIs, automatically converting codes into human-readable formats with sources and timestamps.1438 PyPI11MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search, explore, and query any CKAN open data portal through natural language, making public datasets accessible without requiring knowledge of the portal's API.20696 npm59MIT
TDQS
Scored across 18 tools
Most tools have distinct purposes, but there is some overlap between search_by_attribute and search (both support term + attribute filtering) and between get_data_catalog and get_data_catalog_summary (both retrieve catalog metadata, though with different detail levels). The descriptions help clarify the differences, but an agent might initially confuse these pairs.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_all_data, search_by_location_rectangle). The naming is predictable and uniform across the entire set, making it easy for an agent to understand the action and target.
With 18 tools, the count is slightly high but reasonable for a data platform server covering search, retrieval, metadata, and file operations. Each tool serves a specific function, though some could potentially be consolidated (e.g., multiple search variants).
The toolset comprehensively covers the domain of data access and management, including search (with various filters), data retrieval (batch, single, counts), metadata exploration (catalogs, datasets, municipalities, prefectures), file operations (downloads, thumbnails, ZIPs), and utilities (suggest, normalize). There are no obvious gaps for core workflows.