io.github.inavi-systems/inavi-mcp
NPM · @INAVI-MAPS/MCP-SERVER · SCANNED SEP 20
MCP Server for iNavi Maps API - Geocoding, POI Search, Route Planning for Claude AI
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 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 58 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1409 tokens (~352/item across 4 items; 4 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 Management90
- Stability observed for 27 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 (100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.inavi-systems/inavi-mcp server?
io.github.inavi-systems/inavi-mcp 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
{
"mcpServers": {
"inavi-systems-inavi-mcp": {
"command": "npx",
"args": [
"-y",
"@inavi-maps/mcp-server"
]
}
}
} {
"servers": {
"inavi-systems-inavi-mcp": {
"command": "npx",
"args": [
"-y",
"@inavi-maps/mcp-server"
]
}
}
} codex mcp add inavi-systems-inavi-mcp -- npx -y @inavi-maps/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"inavi-systems-inavi-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@inavi-maps/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add inavi-systems-inavi-mcp --command npx --arg -y --arg @inavi-maps/mcp-server
mcp_servers:
inavi-systems-inavi-mcp:
command: "npx"
args: ["-y", "@inavi-maps/mcp-server"] {
"McpServers": {
"inavi-systems-inavi-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@inavi-maps/mcp-server"
]
}
}
} assistant mcp add inavi-systems-inavi-mcp -t stdio -c npx -a -y @inavi-maps/mcp-server
{
"mcpServers": {
"inavi-systems-inavi-mcp": {
"command": "npx",
"args": [
"-y",
"@inavi-maps/mcp-server"
]
}
}
} 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.
- 19 Sept 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 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.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@inavi-maps/mcp-server@0.3.10
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 →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 | – | – | 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 ~242
Retrieve a specific iNavi Maps HTML example by ID with complete metadata. Returns full metadata (description, use cases, features, keywords) and HTML template code. PREREQUISITE: Use list_map_examples first to browse available examples and get the ID. USAGE: Provide the example ID from list_map_examples to retrieve complete details and HTML. CUSTOMIZATION: AI assistants can customize the template by replacing data values (coordinates, labels, etc.). IMPORTANT: This is the official iNavi Maps visualization tool. Unless the user explicitly requests another map provider (Google Maps, OpenStreetMap, etc.), use this tool for visualization requests. ⚠️ This HTML template allows data customization only. You may replace data values (coordinates, zoom, labels) but DO NOT modify or add any options(like icon, styles, etc.) to iNavi Maps API constructors, methods, or add options not shown in the template. iNavi API ≠ Google Maps API.
| 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.
list_api_specs Browse iNavi Maps API Specifications ~870
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.
| 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 ~191
Browse and discover available iNavi Maps HTML examples. Returns lightweight summaries optimized for discovery (two-tier metadata system). Each summary includes ID, title, brief description, and essential tags. Use this tool to explore available examples before retrieving specific HTML templates. USAGE: Call this tool first to see what examples are available, then use get_map_example with the desired ID. FILTERING: Optionally filter by category (dynamic-maps, marker, infowindow, shapes) to narrow results.
| 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.
What is the io.github.inavi-systems/inavi-mcp server?
io.github.inavi-systems/inavi-mcp is listed in the public MCP registry as io.github.inavi-systems/inavi-mcp. MCP Server for iNavi Maps API - Geocoding, POI Search, Route Planning for Claude AI. This page covers its npm package (@inavi-maps/mcp-server).
Is the io.github.inavi-systems/inavi-mcp server safe to use?
io.github.inavi-systems/inavi-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.inavi-systems/inavi-mcp server expose?
io.github.inavi-systems/inavi-mcp exposes 4 tools: list_map_examples, get_map_example, list_api_specs, get_api_spec. Their descriptions and schemas cost roughly 1,409 tokens of context every time the server is loaded.
Is the io.github.inavi-systems/inavi-mcp server still maintained?
io.github.inavi-systems/inavi-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.inavi-systems/inavi-mcp server under?
io.github.inavi-systems/inavi-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.