iNavi Maps Docs (io.github.inavi-systems/inavi-mcp@0.4.1) The iNavi Maps Docs MCP server, version 0.4.1, was published to the official MCP registry on 2026-09-23 and is distributed as @inavi-maps/mcp-server on npm, according to the mcpindex server index. mcpindex reports that its semantic screen found no manipulation pattern in the server's description, though the deterministic conformance probe has not yet been run and the listing is past its freshness window. The index's gate pins each MCP tool contract and holds calls when a contract drifts without a version bump. ← Index https://mcpindex.ai/leaderboard iNavi Maps Docs iNavi Maps docs for AI South Korea : API specs, Web JS SDK reference, HTML map templates The current version, v0.4.1, was published to the official MCP registry on 2026-09-23. It is distributed as @inavi-maps/mcp-server on npm, filed under Documents & Spreadsheets by this index. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts https://mcpindex.ai/stats put this record in context. Using iNavi Maps Docs in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself use Install this server for that . Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less uv tool install mcpindex-gate && mcpindex-config-wire method https://mcpindex.ai/methodology Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. mcpindex.integrity.description passINFO evidence“No malicious instructions found”via static description - - Semantic screen only - the deterministic conformance probe has not run on this server - - Confidence is reported but not yet calibrated v1 - - Screen reads the tool description, not the live behavior - - advisory - - registry description only no input schema - - screen model 8b - - Past its freshness window - we could not re-confirm this listing - - The description this screen assessed is no longer the one published - - The registry listing version, packages, links changed after this screen ran - the description we assessed did not Semantic screen: an LLM judge reads the tool description for hidden instructions status PARTIAL . A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated calibrated=false at v1 . Full verdict history is not shown on this page. Own this server? Screen its description → https://mcpindex.ai/screen That verdict was true at screening time snapshot 2026-09-23 . Contracts can change after screening, with no version bump. The gate pins iNavi Maps Docs’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. See your first HOLD in 2 minutes → https://mcpindex.ai/guides/install-the-gate-first-hold Related: how to trust an MCP server https://mcpindex.ai/guides/how-to-trust-an-mcp-server · screen before install https://mcpindex.ai/guides/screen-mcp-server-before-install · silent contract drift https://mcpindex.ai/guides/mcp-silent-contract-drift People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land. Independent trust record for iNavi Maps Docs https://mcpindex.ai/server/io-github-inavi-systems-inavi-mcp - screening verdict, registry provenance, and contract drift monitoring.