Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ryanbaumann/platform-ai

NPM · @GOOGLEMAPS/CODE-ASSIST-MCP

Google Maps Platform Code Assist MCP

Available components

npm · @googlemaps/code-assist-mcp 73
−3 this week 73 Trust /100

Last scanned (9 hours ago)

Scores higher than 45% of npm servers

Category Code Search and Documentation

Trust breakdown (7 categories)

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects axios 1.9.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 85 of 226 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency39
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 439 tokens (~146/item across 3 items; 2 tools + 1 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 Management77
  • Stability observed for 23 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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 −3
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-101902 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-101904 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-101908 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2025-58754 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • Stability: pass → 0.77 functional
  • 4 Nov 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-101902 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-101904 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-101908 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2025-58754 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 3 Nov 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-101902 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-101904 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-101908 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2025-58754 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 2 Nov 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-101902 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-101904 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-101908 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2025-58754 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 1 Nov 26 0
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-101902 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-101904 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-101908 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2025-58754 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 31 Oct 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-101902 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-101904 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-101908 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2025-58754 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
  • 15 Oct 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 13 Oct 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

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/@googlemaps/code-assist-mcp@0.2.0

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 33 findings
ID CVE Severity Vector Fix available
GHSA-35jp-ww65-95wh CVE-2026-44494 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N yes
GHSA-3g43-6gmg-66jw CVE-2026-44495 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-3p68-rc4w-qgx5 CVE-2025-62718 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-3w6x-2g7m-8v23 CVE-2026-42044 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N yes
GHSA-42h9-826w-cgv3 CVE-2026-67313 medium yes
GHSA-43fc-jf86-j433 CVE-2026-25639 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-445q-vr5w-6q77 CVE-2026-42037 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-4hjh-wcwx-xvwj CVE-2025-58754 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-5c9x-8gcm-mpgx CVE-2026-42034 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-62hf-57xw-28j9 CVE-2026-42039 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6chq-wfr3-2hj9 CVE-2026-42035 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-777c-7fjr-54vf CVE-2026-44488 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7q8q-rj6j-mhjq CVE-2026-67319 medium yes
GHSA-898c-q2cr-xwhg CVE-2026-44490 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-9fr6-4gfg-395g CVE-2026-101902 medium yes
GHSA-fvcv-3m26-pcqx CVE-2026-40175 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-hfxv-24rg-xrqf CVE-2026-44496 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-j5f8-grm9-p9fc CVE-2026-44486 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-j8rh-479h-cp32 CVE-2026-101904 medium yes
GHSA-jqh4-m9w3-8hp9 CVE-2026-67317 medium yes
GHSA-m7pr-hjqh-92cm CVE-2026-42038 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-mmx7-hfxf-jppx CVE-2026-67316 medium yes
GHSA-p92q-9vqr-4j8v CVE-2026-44487 high yes
GHSA-pf86-5x62-jrwf CVE-2026-42033 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-pmv8-rq9r-6j72 CVE-2026-67312 medium yes
GHSA-pmwg-cvhr-8vh7 CVE-2026-42043 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-q8qp-cvcw-x6jj CVE-2026-42264 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-vf2m-468p-8v99 CVE-2026-42036 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-vh66-26gq-q6x8 CVE-2026-101908 medium yes
GHSA-w9j2-pvgh-6h63 CVE-2026-42041 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-xhjh-pmcv-23jw CVE-2026-42040 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-xx6v-rp6x-q39c CVE-2026-42042 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 226 packages
Packages resolved 226
Deprecated 2
Stale 83
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~363 tokens

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 →

Tool Tokens
retrieve-google-maps-platform-docs ~272

Searches Google Maps Platform documentation, code samples, architecture center, trust center, GitHub repositories (including sample code and client libraries for react-google-maps, flutter, compose, utilities, swiftui, and more), and terms of service to answer user questions. CRITICAL: You MUST call the `retrieve-instructions` tool or load the `instructions` resource BEFORE using this tool. This provides essential context required for this tool to function correctly.

NameTypeReqDescription
promptstringyesYou are an expert prompt engineer for a Retrieval-Augmented Generation (RAG) system. **Instructions:** 1. Analyze the user's intent (e.g., are they trying to implement, troubleshoot, or learn?). 2.…
search_contextarray–Supplemental context to aid the search if the prompt alone is ambiguous or too broad. Put names of existing Google Maps Platform products or features specified in the user prompt.

No output schema declared.

No examples provided.

retrieve-instructions ~91

CRITICAL: Call this tool first for any queries related to location, mapping, addresses, routing, points of interest, location analytics, or geospatial data (e.g., Google Earth). It provides the foundational context on Google Maps Platform (APIs for maps, routes, and places) and best practices that are essential for the other tools to function correctly. This tool MUST be called before any other tool.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.ryanbaumann/platform-ai MCP server?

io.github.ryanbaumann/platform-ai runs locally as an npm package, launched with npx -y @googlemaps/code-assist-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @googlemaps/code-assist-mcp

# add to Claude Code
claude mcp add ryanbaumann-platform-ai -- npx -y @googlemaps/code-assist-mcp
Common questions

What is the io.github.ryanbaumann/platform-ai MCP server?

io.github.ryanbaumann/platform-ai is an MCP server listed in the public MCP registry as io.github.ryanbaumann/platform-ai. Google Maps Platform Code Assist MCP. This page covers its npm package (@googlemaps/code-assist-mcp).

Is the io.github.ryanbaumann/platform-ai MCP server safe to use?

io.github.ryanbaumann/platform-ai scores 73 out of 100 on VerifyMCP. We recorded 33 known advisories 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 io.github.ryanbaumann/platform-ai MCP server expose?

io.github.ryanbaumann/platform-ai exposes 2 tools: retrieve-google-maps-platform-docs, retrieve-instructions. Their descriptions and schemas cost roughly 363 tokens of context every time the server is loaded.

Is the io.github.ryanbaumann/platform-ai MCP server still maintained?

io.github.ryanbaumann/platform-ai 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 io.github.ryanbaumann/platform-ai MCP server under?

io.github.ryanbaumann/platform-ai declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.