oyama-opendata-mcp
Related Servers
Alternatives to oyama-opendata-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for accessing Japanese government statistics portal 'e-Stat' API, enabling language models to search and retrieve statistical data.521MIT
- AlicenseAqualityAmaintenanceModel Context Protocol (MCP) server providing access to 155 normalized Japanese public open datasets (10.16M+ records) including GEPS procurement, healthcare, land prices, and DuckDB SQL.315MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Japan's e-Stat (Government Statistics Portal). Search statistical datasets, retrieve data tables, and access metadata from official Japanese government statistics.39 PyPI10Apache 2.0
- AlicenseAqualityCmaintenanceMCP server for Japanese public business data, enabling AI agents to validate and look up corporate numbers, search bank/branch codes, and check national holidays. Runs locally with no telemetry; live corporate registry data requires a free NTA app ID.8MIT
- AlicenseBqualityBmaintenanceMCP server for the Japan National Tax Agency Corporate Number API, enabling corporate number lookup and search via local AI clients.31MIT

city-data-mcpofficial
AlicenseAqualityDmaintenanceAn MCP server that gives Claude deep access to US public data -- demographics, economics, crime, employment, weather, housing, transit, schools, budgets, and more across 30+ cities for government intelligence workflows.28MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: get_age_distribution returns age pyramids, get_population returns population counts, get_metadata returns source information, list_areas returns filtering options, and list_datasets returns available datasets. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using underscores: get_* for data retrieval and list_* for enumerations. The naming is predictable and readable.
With 5 tools, the set is well-scoped for an open data MCP focused on population demographics. Each tool serves a necessary role without redundancy or unnecessary complexity.
The tool surface covers core operations: listing datasets and areas, retrieving age distribution and population data, and accessing metadata. Minor gaps exist (e.g., no direct tool for household composition), but the main query needs are addressed.