Japan Geospatial Open Data MCP server
by atushi1841·
io.github.atushi1841/japan-geospatial-open-data-mcp·v1.0.6Japan geospatial MCP: Apify:apify.com/fruitful_quintessence | Gumroad:atushi5.gumroad.com/l/kutuxe
A88/100grade A
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Japan Geospatial Open Data yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Japan Geospatial Open Data tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-24 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Japan Geospatial Open Data compares
Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 70% of 868 Scraping and browsing servers
Install Japan Geospatial Open Data in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
Japan Geospatial Open Data: common questions
- Is Japan Geospatial Open Data MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Japan Geospatial Open Data safety report
- Does Japan Geospatial Open Data need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Japan Geospatial Open Data maintained?
- The last commit was 9 days ago (2026-10-24). The latest release is v1.0.6.