mcp-google-map-project — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mcp-google-map-project (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill contains everything needed to develop, maintain, and extend the @cablate/mcp-google-map MCP server. Reading these files gives you full context on architecture, API specifics, domain knowledge, and the reasoning behind design decisions.
For the agent skill (how to USE the tools), see skills/google-maps/SKILL.md.
| Aspect | Summary |
|---|---|
| What | MCP server providing Google Maps tools for AI agents |
| Stack | TypeScript, Node.js, Express, MCP SDK, Zod |
| Tools | 17 tools (14 atomic + 3 composite) |
| Transports | stdio, Streamable HTTP, standalone exec CLI |
| APIs | Places API (New), Directions, Geocoding, Elevation, Timezone, Weather, Air Quality, Static Maps, Search Along Route |
| File | Content | When to read |
|---|---|---|
references/architecture.md | System architecture, 3-layer design, transport modes, tool registration flow, 9-file checklist, code map | Start here when onboarding. Also read when adding new tools. |
references/google-maps-api-guide.md | All Google Maps API endpoints used, pricing, coverage limits, rate limits, common gotchas, Places New vs Legacy | When debugging API errors, evaluating new APIs, or checking costs |
references/geo-domain-knowledge.md | GIS fundamentals — coordinates, distance, geocoding, place types, spatial search, map projection, Japan-specific knowledge | When making tool design decisions that involve geographic concepts |
references/decisions.md | 10 Architecture Decision Records (ADR) with context and rationale | When asking "why was X built this way?" or considering changes to existing design |
See references/architecture.md § "9-File Tool Change Checklist" for the complete procedure. Summary:
src/tools/maps/<toolName>.ts (NAME, DESCRIPTION, SCHEMA, ACTION)src/config.tssrc/cli.tstests/smoke.test.ts (expectedTools + API call test)README.md (count + table + exec list + project structure)skills/google-maps/SKILL.md (Tool Map)skills/google-maps/references/tools-api.md (params + chaining)server.json and package.json descriptions| Trigger | What to update |
|---|---|
| Architecture change | references/architecture.md |
| New Google Maps API integrated | references/google-maps-api-guide.md |
| New design decision made | references/decisions.md (add ADR) |
| New GIS concept relevant to tools | references/geo-domain-knowledge.md |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.