Official description7 sourcesMCP servers8d ago
Flightmussy/castlemap-mcp
Castlemap MCP server A Model Context Protocol server for the Castlemap atlas: 7,786 castles, fortresses, palaces and ruins across 141 countries, with coordinates, founding dates, categories, fame ranking and Wikipedia summaries.
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add castlemap-mcp -- npx -y castlemap-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 1 ★ · Flightmussy/castlemap-mcp · read from the repository page · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
- Score
- score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Flightmussy/castlemap-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
Castlemap MCP server
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A Model Context Protocol server for the
Castlemap atlas: 7,786 castles, fortresses, palaces and ruins across 141 countries,
with coordinates, founding dates, categories, fame ranking and Wikipedia
summaries.
It is already running. Point a client at the hosted endpoint — there is no
install, no signup and no API key:
Streamable HTTP, stateless, POST-only (a GET returning 405 is correct).
Protocol revisions 2025-06-18 and 2025-03-26 are accepted.
Client configuration
Registry entry: com.thecastlemap/castles.
Tools
| Tool | What it does |
| --- | --- |
| search_castles | Find castles by name, country or category |
| get_castle | Full record for one castle |
| castles_near | Nearest castles to a coordinate (haversine); geocode first |
| top_castles | Best-known castles, by fame rank |
| list_countries | The 141 countries, with counts |
| get_statistics | Live aggregates — totals, per-country, per-century |
| random_castle | One castle at random |
Data
Derived from Wikidata, with summaries from
Wikipedia and images from Wikimedia Commons. The atlas is curated rather than
exhaustive: it covers castles with a documented history, a real photo and exact
coordinates, not every earthwork and ruin.
The factual records are released as **CC0** and downloadable as GeoJSON and CSV
from thecastlemap.com/data — also mirrored on
GitHub,
Hugging Face,
Kaggle
and Zenodo (concept DOI
10.5281/zenodo.21322359, which always resolves to the newest version).
Running it yourself
server.mjs has **zero dependencies** — no SDK, no node_modules. It needs
Node 18+ and a castles.geojson to read (download one from
/data):
It binds 127.0.0.1:8891 by default; HOST, PORT and CASTLES_GEOJSON
override that. The file is re-read when its mtime changes (throttled to 60s), so
updating the data needs no restart.
castlemap-mcp.service is the systemd unit used in production — loopback-bound,
DynamicUser, ProtectSystem=strict, with nginx terminating TLS in front. Set
ExecStart to your own node path and ReadOnlyPaths/CASTLES_GEOJSON to
wherever the data lives.
Provenance
Built by flightmussy with AI assistance: the concept,
Castlemap atlas: 7,786 castles, fortresses, palaces and ruins across 141 countries,
with coordinates, founding dates, categories, fame ranking and Wikipedia
summaries.
It is already running. Point a client at the hosted endpoint — there is no
install, no signup and no API key:
Streamable HTTP, stateless, POST-only (a GET returning 405 is correct).
Protocol revisions 2025-06-18 and 2025-03-26 are accepted.
Client configuration
Registry entry: com.thecastlemap/castles.
Tools
| Tool | What it does |
| --- | --- |
| search_castles | Find castles by name, country or category |
| get_castle | Full record for one castle |
| castles_near | Nearest castles to a coordinate (haversine); geocode first |
| top_castles | Best-known castles, by fame rank |
| list_countries | The 141 countries, with counts |
| get_statistics | Live aggregates — totals, per-country, per-century |
| random_castle | One castle at random |
Data
Derived from Wikidata, with summaries from
Wikipedia and images from Wikimedia Commons. The atlas is curated rather than
exhaustive: it covers castles with a documented history, a real photo and exact
coordinates, not every earthwork and ruin.
The factual records are released as **CC0** and downloadable as GeoJSON and CSV
from thecastlemap.com/data — also mirrored on
GitHub,
Hugging Face,
Kaggle
and Zenodo (concept DOI
10.5281/zenodo.21322359, which always resolves to the newest version).
Running it yourself
server.mjs has **zero dependencies** — no SDK, no node_modules. It needs
Node 18+ and a castles.geojson to read (download one from
/data):
It binds 127.0.0.1:8891 by default; HOST, PORT and CASTLES_GEOJSON
override that. The file is re-read when its mtime changes (throttled to 60s), so
updating the data needs no restart.
castlemap-mcp.service is the systemd unit used in production — loopback-bound,
DynamicUser, ProtectSystem=strict, with nginx terminating TLS in front. Set
ExecStart to your own node path and ReadOnlyPaths/CASTLES_GEOJSON to
wherever the data lives.
Provenance
Built by flightmussy with AI assistance: the concept,
- Source
- awesome · https://github.com/Flightmussy/castlemap-mcp
- Browse by field
- MCP servers
- Traction
- 1 ★
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.