jiangshan-map
Related Servers
Alternatives to jiangshan-map
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables querying of China Historical Geographic Information System (CHGIS) database for historical place names, administrative divisions, and geographical data from 222 BCE to 1911 CE. Supports searching by place ID, name, year, administrative type, and retrieving historical context and hierarchical relationships.33MIT
- AlicenseAqualityCmaintenanceA traceable Chinese-history MCP server that enables querying of nine classical Chinese texts (e.g., 史记, 汉书) with citations and honest status labels. It provides four tools to search events, persons, places, and qualities, all with provenance.430 PyPI3MIT
- AlicenseAqualityCmaintenanceHistorical geography for AI agents: 1,000+ polities with real GeoJSON borders, dynastic succession chains, events, cities and trade routes from 4500 BCE to today, each with cited academic sources and a confidence score. Wraps the free AtlasPI REST API (https://atlaspi.it) as 39 MCP tools — no API key required, Apache-2.0.391Apache 2.0

Timepoint MCPofficial
FlicenseNot gradedqualityBmaintenanceProvides structured access to a temporal knowledge platform for searching historical events and browsing a causal graph of over 2,000 years of history. It enables users to generate rich historical scenes, interact with period-appropriate characters, and run complex temporal simulations.-- FlicenseNot gradedqualityDmaintenanceEnables querying 10,000 years of historical social-complexity data from the Seshat Global History Databank through 9 tools, allowing counterfactual analysis and comparison of polities in natural language.1-
- AlicenseNot gradedqualityBmaintenanceEnables users to search Chinese poems by title, content, author, dynasty, or category; check recitations and dictation; generate appreciation text; create TTS recitations with subtitles; and produce calligraphy practice sheets.MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct roles: inspect_place retrieves place context, inspect_person retrieves person/compare context, and search_atlas performs cross-entity discovery. While search can surface cities or figures also handled by the inspect tools, the search-vs-inspect boundary is explicit and easy for an agent to apply.
All names follow a consistent verb_noun pattern: inspect_place, inspect_person, search_atlas. The convention is predictable and readable, with no mixing of camelCase, vague verbs, or inconsistent action styles.
Three tools is minimal but reasonable for a focused read-only historical atlas: one discovery tool and two entity-specific inspectors. It sits at the low end of the appropriate range, so it is slightly thin but not mismatched to the purpose.
The surface covers the core read-only workflows: search across the atlas, inspect a place or route, and inspect/compare people. Minor gaps remain, such as no dedicated timeline/era browse or explicit list operation, but search_atlas mitigates these enough that agents can work around them.