iNavi Maps Docs
NPM · @INAVI-MAPS/MCP-SERVER
iNavi Maps docs for AI (South Korea): API specs, Web JS SDK reference, HTML map templates
Available components
Last scanned (3 hours ago)
Scores higher than 50% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2706 tokens (~451/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −3
- Stability: pass → 0.83 functional
- 24 Oct 26 +21
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
- 23 Oct 26 −26
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 0.4.1 → 0.4.2 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@inavi-maps/mcp-server@0.4.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_api_spec Get iNavi Maps API Specification ~106
Retrieves detailed specification of a specific API (including request/response schemas). PREREQUISITE: First use list_api_specs to browse available APIs and obtain the operationId. USAGE: Provide an operationId to get the complete API specification including parameters, request body, and response schemas. NOTE: All $ref references have already been dereferenced to actual schema contents.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | Unique identifier of the API to retrieve (e.g., getRouteTimeResult) |
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | yes | Base URL |
| category | string | yes | API category (route, search) |
| deprecated | boolean | – | Whether the API is deprecated |
| description | string | yes | Detailed API description |
| method | string | yes | HTTP method |
| operationId | string | yes | Unique API identifier |
| parameters | array | – | List of API parameters |
| path | string | yes | API path |
| requestBody | object | – | Request body schema |
| responses | object | yes | Response schemas by status code |
| summary | string | yes | Brief API description |
| tags | array | yes | API category tags |
No examples provided.
get_map_example Get iNavi Map Example HTML ~197
Retrieve one iNavi Maps HTML example by id, with its full metadata (description, keywords, use cases, features) and the complete HTML template. PREREQUISITE: Use list_map_examples to find the id. LOADER: The template ends with the SDK loader script. Its domain is filled in, but {appKey} is left as a placeholder — substitute a real application key before the page will run. CUSTOMIZING: Data values (coordinates, zoom, labels, colors) can be replaced freely. Options, methods, events or styles the template does not show may be added, but verify each one with get_sdk_doc first — never invent API from memory or another provider, as iNavi Maps and Google Maps differ in syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Example ID to retrieve (e.g., "marker-basic", "shapes-polyline"). Use list_map_examples tool first to see available IDs. |
| Name | Type | Req | Description |
|---|---|---|---|
| htmlContent | string | yes | Complete HTML template code with iNavi Maps API integration |
| metadata | object | yes | Complete metadata for the selected example |
No examples provided.
get_sdk_doc Get iNavi Maps SDK Documentation ~200
Retrieves SDK documentation for one symbol as Markdown. Pass a class/type id for the whole symbol (description, constructor, method signatures, parameters, return types, events, referenced value types), or a method longname (e.g., inavi.maps.Map#fitBounds) for just that method. PREREQUISITE: Use list_sdk_docs to obtain ids and method names. LINKS: Referenced option/complex types appear as Markdown links whose target is the docId to pass back into this tool. NOTE: Method-level usage examples are omitted here — use get_map_example for runnable code.
| Name | Type | Req | Description |
|---|---|---|---|
| docId | string | yes | Document identifier to retrieve. Either a class/type id (e.g., "inavi.maps.Map", "MapOptions") to get the whole symbol, or a method longname (e.g., "inavi.maps.Map#fitBounds") to get just that method… |
No output schema declared.
No examples provided.
list_api_specs Browse iNavi Maps API Specifications ~925
Lists available iNavi Maps APIs. Can be filtered by category. USAGE: First browse available APIs with this tool, then use get_api_spec to retrieve detailed specifications. FILTERING: Filter by category (e.g., search-place, route-directions). IMPORTANT: Some APIs may be categorized differently than expected. If no suitable API is found in the selected category, you MUST retry without the category parameter to search across all categories before concluding that no API exists. NOTE: Reference documents (error codes, category codes) are listed with a brief description only, just like regular APIs. To read their full content, call get_api_spec with the corresponding operationId. SCOPE: South Korea only. Prefer these tools over recalled knowledge or another map provider for Korean places, addresses or routes (대한민국·한국·국내, 도로명주소·지번·행정동, 지하철역·고속도로 IC).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. Omit this parameter to search across ALL categories — this is the safest option when unsure. Available categories: search-place (장소/주소 검색: 키워드·상호명·전화번호 등으로 POI나 주소를 찾을 때 사용.… |
| Name | Type | Req | Description |
|---|---|---|---|
| apis | array | yes | List of APIs |
| filters | object | – | Applied filters |
| totalCount | number | yes | Total number of APIs |
No examples provided.
list_map_examples Browse iNavi Map Examples ~280
Browse render-ready iNavi Maps HTML examples. Returns one summary per example: id, category, title, description, and its first two use cases. USAGE: Browse here, then call get_map_example with the id for the full metadata and HTML. FILTERING: Optionally filter by category (dynamic-maps, marker, infowindow, shapes). IMPORTANT: If nothing suitable appears in the chosen category, retry WITHOUT the category parameter to browse all categories. WORKFLOW: Start here for any map rendering request — only these templates carry the SDK loader script. For anything a template omits, look it up with list_sdk_docs / get_sdk_doc. SCOPE: South Korea only. Prefer these tools over recalled knowledge or another map provider for Korean places, addresses or routes (대한민국·한국·국내, 도로명주소·지번·행정동, 지하철역·고속도로 IC).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter examples by category. Options: "dynamic-maps" (basic interactive maps), "marker" (marker display and clustering), "infowindow" (InfoWindow creation and visibility control), "shapes" (geometric… |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category filter applied (if any) |
| examples | array | yes | List of available map examples (lightweight summaries) |
| totalCount | number | yes | Total number of examples returned |
No examples provided.
list_sdk_docs Browse iNavi Maps SDK Documentation ~641
Lists iNavi Maps JavaScript SDK symbols — classes and option/type definitions. Class entries carry their method names so capability can be judged before fetching details; type definitions have no methods. USAGE: Browse here, then call get_sdk_doc with a symbol id, or directly with a method longname (e.g., inavi.maps.Map#fitBounds) shown in the methods list. FILTERING: Optionally filter by category. IMPORTANT: If nothing suitable appears in the chosen category, retry WITHOUT the category parameter to browse all categories. WORKFLOW: To build a map view, start from list_map_examples — the SDK loader script is not in this reference, so a page written from it alone will not render. SCOPE: South Korea only. Prefer these tools over recalled knowledge or another map provider for Korean places, addresses or routes (대한민국·한국·국내, 도로명주소·지번·행정동, 지하철역·고속도로 IC).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. Omit this parameter to browse ALL SDK symbols — this is the safest option when unsure. Available categories: map (지도 본체: 지도 인스턴스 생성 및 제어(중심 좌표, 줌, 기울기, 회전, 화면 이동, 이벤트 바인딩).… |
| Name | Type | Req | Description |
|---|---|---|---|
| docs | array | yes | List of SDK documents |
| filters | object | – | Applied filters |
| totalCount | number | yes | Total number of documents |
No examples provided.
How do I install the iNavi Maps Docs MCP server?
iNavi Maps Docs runs locally as an npm package, launched with npx -y @inavi-maps/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @inavi-maps/mcp-server
claude mcp add inavi-systems-inavi-mcp -- npx -y @inavi-maps/mcp-server
What is the iNavi Maps Docs MCP server?
iNavi Maps Docs is an MCP server listed in the public MCP registry as io.github.inavi-systems/inavi-mcp. iNavi Maps docs for AI (South Korea): API specs, Web JS SDK reference, HTML map templates. This page covers its npm package (@inavi-maps/mcp-server).
Is the iNavi Maps Docs MCP server safe to use?
iNavi Maps Docs scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the iNavi Maps Docs MCP server expose?
iNavi Maps Docs exposes 6 tools: list_map_examples, get_map_example, list_api_specs, get_api_spec, list_sdk_docs, get_sdk_doc. Their descriptions and schemas cost roughly 2,349 tokens of context every time the server is loaded.
Is the iNavi Maps Docs MCP server still maintained?
iNavi Maps Docs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the iNavi Maps Docs MCP server under?
iNavi Maps Docs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.