Korea Local Data: Naver Map & Kakao Map vs INAVI Maps API
Korea Local Data: Naver Map & Kakao Map is an MCP server published by experimory-crypto. Marketplaces we read that list it: 1 (Official MCP Registry). INAVI Maps API is an MCP server published by inavi-systems. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Korea Local Data: Naver Map & Kakao Map |  INAVI Maps API |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.0.4 Downloads/month (npm): 774 Downloads/week (npm): 95 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Korea Local Data: Naver Map & Kakao Map | INAVI Maps API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (magenta-courser--korea-local-data-mcp.apify.actor/mcp) | On your machine (@inavi-maps/api-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/experimory-crypto/naver-map-scraper-examples | github.com/inavi-systems/inavi-api-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-11 | 2026-10-23 |
| Endpoint at the last check (differs) | Responded 19 h ago, requires authentication | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Korea Local Data: Naver Map & Kakao Map
Search Korean places and read reviews from Naver Map and Kakao Map. Pay per result via Apify.
INAVI Maps API
INAVI Maps API for AI (South Korea): place search, geocoding, routes on an interactive map
How to run each
Korea Local Data: Naver Map & Kakao Map As a remote MCP server
claude mcp add --transport http korea-local-data https://magenta-courser--korea-local-data-mcp.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
INAVI Maps API As a local MCP server: npm package
claude mcp add --env "INAVI_APPKEY=<YOUR_INAVI_APPKEY>" --transport stdio inavi-api-mcp -- npx -y @inavi-maps/api-mcp-serverRequires: INAVI_APPKEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Korea Local Data: Naver Map & Kakao Map has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Korea Local Data: Naver Map & Kakao Map publish no settings it asks for, so we do not compare settings.
What it can do: Korea Local Data: Naver Map & Kakao Map · What it can do: INAVI Maps API · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.