Gachi Data API — Japan Station & Accessibility Data vs ShotAPI
In-depth architectural comparison of the Gachi Data API — Japan Station & Accessibility Data and ShotAPI MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Gachi Data API — Japan Station & Accessibility Data
Browser Automation · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
ShotAPI
Browser Automation · Remote HTTP/SSE
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Gachi Data API — Japan Station & Accessibility Data if you need specialized Browser Automation tools running via a hosted cloud SSE transport. Choose ShotAPI if your workspace requires Browser Automation integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Gachi Data API — Japan Station & Accessibility Data when:
You need dedicated capabilities in the Browser Automation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Gachi Data API — Japan Station & Accessibility Data Tools (3)
get_toilet_by_station
Accessible toilets in a Tokyo station, with `nearest_exit
get_public_toilet_by_city
Public toilets in a municipality (top 50 for large cities)
get_station_hazard
Official MLIT hazard categories at a station (flood / liquefaction / storm-surge), relayed live, cached 14 days — no derived score. Landslide & tsunami are license-restricted (`available:false` + link to official maps). Not a substitute for official hazard maps.
ShotAPI Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Gachi Data API — Japan Station & Accessibility Data Configuration
Gachi Data API — Japan Station & Accessibility Data is categorized under Browser Automation and uses a remote streaming HTTP/SSE transport. In contrast, ShotAPI belongs to Browser Automation using remote streaming HTTP/SSE transport. Select Gachi Data API — Japan Station & Accessibility Data when you need capabilities focused on browser automation and ShotAPI when you require tools for browser automation.