io.github.chrischall/gogcli-mcp-maps
NPM · GOGCLI-MCP-MAPS
Google Places + trip maps via gogcli for Claude — places through gog maps, pins, shortlists, My Maps
Available components
Last scanned (14 hours ago)
Scores higher than 77% 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 Security100
- 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
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chrischall/gogcli-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2664 tokens (~222/item across 12 items; 12 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 Management43
- Stability observed for 13 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +16
- Tool safety: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: 1.00 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 4.11.0 → 4.12.0 functional
- Package version: 4.11.0 → 4.11.1 functional
- 8 Nov 26 64
First indexed and scored.
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 21 Nov 2026 · Analysed npm/gogcli-mcp-maps@4.12.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chrischall/gogcli-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chrischall/gogcli-mcp/.github/workflows/release-please.yml@refs/heads/main |
| Rekor log index | 3765634362 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6773aa07dd1645c9d4321be8f1cb9b7b9be779d8d05c333f6716bbb6a5b17e75e7c39458247082834e841dacc8cf4f6ae21e2389fd94cf373899d1414 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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 →
gog_auth_add ~251
Authorize a Google account via browser-based OAuth. Opens a browser window where the user must sign in and grant access. Blocks for up to 5 minutes waiting for the user to complete authorization. If the browser does not open automatically, a fallback URL is included in the response. Use gog_auth_list to check which accounts are already configured.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Google account email to authorize | |
| extraScopes | string | – | Additional raw OAuth scope URIs to request, comma-separated, on top of the ones `services` implies. Use for scopes no service covers — e.g. https://www.googleapis.com/auth/bigquery.readonly, required… |
| services | string | – | Services to authorize: "all" or comma-separated list (e.g. "sheets,gmail,calendar"). Default: "drive". Prefer the narrowest set you need — requesting a service whose Google API is not enabled on the… |
No output schema declared.
No examples provided.
gog_auth_add_complete ~211
Complete REMOTE/headless Google authorization (step 2 of 2). Takes the full redirected localhost URL the user copied after finishing gog_auth_add_url, exchanges it for a refresh token, and stores it. Use the SAME `services` value you passed to gog_auth_add_url. Must run within 10 minutes of step 1 and against the same gogcli host.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Google account email being authorized (same as step 1) | |
| extraScopes | string | – | Extra OAuth scope URIs — MUST match the value passed to gog_auth_add_url, for the same reason `services` must: the two steps have to describe the same grant. |
| redirectUrl | string | yes | The full localhost redirect URL the user copied from the browser address bar after signing in (contains code and state; the page itself fails to load, which is expected). |
| services | string | – | Services authorized — MUST match the value passed to gog_auth_add_url. Default: "drive". |
No output schema declared.
No examples provided.
gog_auth_add_url ~337
Begin REMOTE/headless Google authorization (step 1 of 2). Returns a sign-in URL to open in any browser — no local server or terminal on the gogcli host is needed, so this works on a hosted deployment where the interactive gog_auth_add cannot. Hand the URL to the user; after they sign in, the browser is redirected to a localhost URL that fails to load — that is expected. They copy that full redirected URL (from the address bar) and you pass it to gog_auth_add_complete. The link is valid for 10 minutes. If you pass a custom `services` here, pass the SAME value to gog_auth_add_complete or the second step will not match this one.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Google account email to authorize | |
| extraScopes | string | – | Additional raw OAuth scope URIs to request, comma-separated, on top of the ones `services` implies. Use for scopes no service covers — e.g. https://www.googleapis.com/auth/bigquery.readonly, required… |
| services | string | – | Services to authorize: "all" or comma-separated list (e.g. "sheets,gmail,calendar"). Default: "drive". Prefer the narrowest set you need — requesting a service whose Google API is not enabled on the… |
No output schema declared.
No examples provided.
gog_auth_health ~198
Check the LIVE health of each stored Google account. Unlike gog_auth_status (which only reports keyring/config setup), this performs a real token refresh against Google, so it detects expired or revoked (invalid_grant) refresh tokens — the account-wide sign-out that blocks every service. Reports per account: whether the token is currently valid, the mapped cause when it is not, how long ago it was authorized, and a warning as it approaches the 7-day refresh-token limit that applies to OAuth apps whose consent screen is still in "Testing" mode. Run it proactively to re-authorize on your own schedule instead of mid-task. On a hosted deployment this is the ONLY check that measures Google: a connector showing "connected" or "refreshed" has verified the client's connection to the MCP host, and nothing else — the Google credential lives in gog's keyring on that host and can be dead while the connection looks perfectly healthy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gog_auth_list ~81
List the Google accounts stored in gogcli, with their scopes. This reads local configuration only — it does not contact Google and does NOT tell you whether an account still works: a signed-out account whose refresh token expired or was revoked is listed here exactly like a healthy one, scopes and all. Use gog_auth_health to check whether an account can actually authenticate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gog_auth_run ~230
Run any gog auth subcommand not covered by the other tools. Run `gog auth --help` for the full list of subcommands, or `gog auth <subcommand> --help` for flags on a specific subcommand. Only these subcommands are available: list, status, services, alias. Flags that override server safety controls (--readonly, --enable-commands, --disable-commands, --account, --access-token, --home, --client, --gmail-no-send, --no-input) and a bare "--" are refused. Local file paths (--out, --out-dir, --attach, --file, --*-file, @file JSON) must be inside GOG_FILE_ROOTS; subcommands that take a local path positionally (e.g. drive upload) are refused in favour of their dedicated tools. For browser-based authorization, use gog_auth_add instead.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional positional args and flags |
| subcommand | string | yes | The gog auth subcommand to run, e.g. "alias", "list", "status" |
No output schema declared.
No examples provided.
gog_auth_services ~24
List all Google services supported by gogcli and the OAuth scopes each requires.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gog_auth_status ~66
Show gogcli auth CONFIGURATION: keyring backend, credential files, and auth setup. Despite the name this is not a health check — it reads local setup and does not contact Google, so it says nothing about whether an account can still authenticate. Use gog_auth_health for that.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gog_places_details ~156
Look up one Google place id: name, address, Google Maps link and lat/lng. Runs `gog maps places details` and `gog maps geocode`; free when cached (content 24 h, coordinates 30 days); refresh: true bypasses the cache. Each result has a status: ok (place found, pin exact or given), approximate (the pin is the geocoded address, not the place itself, or there is no pin), not_found, or error.
| Name | Type | Req | Description |
|---|---|---|---|
| placeId | string | yes | Google place id (from search/resolve), with or without "places/" |
| refresh | boolean | – | Ignore cached entries and look up again (each lookup is a billed Google request through gog) |
No output schema declared.
No examples provided.
gog_places_resolve ~225
Resolve a list of named stops (1-50) to Google places: place id, address, Maps link and lat/lng, each from the top match for "name, address, near" (or `gog maps places details` for a known place_id), with the point from `gog maps geocode`. Flags a top match whose name does not match as ambiguous. Up to 4 lookups run at once; a cancelled call starts no more. Cached per Google policy (ids kept, coordinates 30 days, everything else 24 h), so re-resolving the same list is free; refresh: true bypasses the cache. Each result has a status: ok (place found, pin exact or given), approximate (the pin is the geocoded address, not the place itself, or there is no pin), not_found, or error.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Stops to resolve (1-50) |
| refresh | boolean | – | Ignore cached entries and look up again (each lookup is a billed Google request through gog) |
No output schema declared.
No examples provided.
gog_places_search ~175
Find ONE place on Google by free text (the single top match) and return its place id, name, address, Google Maps link and lat/lng. Runs `gog maps places search`, then `gog maps geocode` on the address for the coordinates (cached). Each result has a status: ok (place found, pin exact or given), approximate (the pin is the geocoded address, not the place itself, or there is no pin), not_found, or error.
| Name | Type | Req | Description |
|---|---|---|---|
| near | string | – | Area hint appended to the search text, e.g. "Tampa, FL" (gog has no location bias, so this is plain text) |
| query | string | yes | What to look for, e.g. "Armature Works" or "Cuban sandwich Ybor City" |
No output schema declared.
No examples provided.
gog_trip_map ~710
Turn a trip itinerary into PINS ON A MAP (not a route): resolves each stop to a Google place through gog (`gog maps places search`/`details` + `gog maps geocode`, cached), warns first about approximate pins, ambiguous matches and unresolved stops, and returns each stop's status and Google Maps pin link grouped by day, with Google Maps shortlist links per day (and for the whole trip when it has at most 20 places) that let the user save the places to their Google Maps Lists. Writes a KML (one folder per day, one colour per category) and a CSV, uploads both to Drive "Trips/<title>" (reused on re-runs; same-named files replaced), and gives the 3 steps to import the KML into Google My Maps (My Maps and Maps Lists have no API). With share_with + confirm_share: true, shares the folder as reader with those emails only, after the user confirms; never public. GOG_READONLY or upload: false → nothing goes to Drive; the files are returned inline. If the client cannot show that prompt (no MCP elicitation, e.g. claude.ai), a two-step flow applies instead: call WITHOUT confirmToken and nothing is sent or changed — the result has status "confirmation-required", the full preview and a confirmToken. Follow its instruction (by default: show the preview to the user verbatim and only after they explicitly approve it in chat, call again with the SAME arguments plus confirmToken). The tool re-reads what it would act on and refuses (DRAFT_CHANGED, with a fresh preview and token) if it changed; TOKEN_EXPIRED / TOKEN_REUSED / TOKEN_INVALID also do nothing. A server set to MCP_CONFIRM_MODE=refuse refuses instead.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Google account email to use, e.g. you@gmail.com — must be the full address, not a bare username. Overrides the GOG_ACCOUNT env var. Omit to use the single configured account. |
| confirmToken | string | – | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se… |
| confirm_share | boolean | – | Must be true for share_with to be acted on |
| drive_parent | string | – | Drive folder id to hold "Trips" (default: My Drive root) |
| share_with | array | – | Emails to share the Drive folder with as reader |
| start_date | string | – | YYYY-MM-DD of day 1, so numbered days get dates |
| stops | array | yes | The stops (1-100), in any order |
| title | string | yes | Trip title: the map, folder and file name |
| upload | boolean | – | Upload to Drive (default true); false keeps the files local/inline |
| view | string | – | Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact (the default) gives the days, pins and files. full… |
No output schema declared.
No examples provided.
How do I install the io.github.chrischall/gogcli-mcp-maps server?
io.github.chrischall/gogcli-mcp-maps runs locally as an npm package, launched with npx -y gogcli-mcp-maps. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · gogcli-mcp-maps
claude mcp add chrischall-gogcli-mcp-maps -- npx -y gogcli-mcp-maps
What is the io.github.chrischall/gogcli-mcp-maps server?
io.github.chrischall/gogcli-mcp-maps is listed in the public MCP registry as io.github.chrischall/gogcli-mcp-maps. Google Places + trip maps via gogcli for Claude, places through gog maps, pins, shortlists, My Maps. This page covers its npm package (gogcli-mcp-maps).
Is the io.github.chrischall/gogcli-mcp-maps server safe to use?
io.github.chrischall/gogcli-mcp-maps scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.chrischall/gogcli-mcp-maps server expose?
io.github.chrischall/gogcli-mcp-maps exposes 12 tools: gog_auth_list, gog_auth_status, gog_auth_health, gog_auth_services, gog_auth_add, and 7 more. Their descriptions and schemas cost roughly 2,664 tokens of context every time the server is loaded.
Is the io.github.chrischall/gogcli-mcp-maps server still maintained?
io.github.chrischall/gogcli-mcp-maps is still listed as active in the MCP registry. We last reached this channel on 21 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.chrischall/gogcli-mcp-maps server under?
io.github.chrischall/gogcli-mcp-maps declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.chrischall/gogcli-mcp-maps server?
VerifyMCP ran 16 checks on io.github.chrischall/gogcli-mcp-maps, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.