[Target] Add Google Maps MCP to the Safety Index

[KryptosAI]

Task

Run MCP Observatory against Google Maps MCP (@anthropic/mcp-server-google-maps) and add a Safety Index target.

Why this matters

Google Maps MCP enables agents to geocode addresses, search places, and retrieve directions. The security surface includes API key exposure, location data leakage, and usage of a paid Google Cloud API that could incur costs if misused.

Steps

1. Run the scan: npx @kryptosai/mcp-observatory test npx -y @anthropic/mcp-server-google-maps
2. Generate the report: npx @kryptosai/mcp-observatory report --run <artifact.json> --format markdown
3. Add artifacts to docs/safety-index/artifacts/google-maps-mcp-server.{json,md}
4. Add entry to docs/safety-index/targets.json
5. Update the safety index table in docs/mcp-server-safety-index.md
6. Run npm run safety-index and npm test

Safe mode

The tool listing works without a Google API key — the scan runs in metadata-only safe mode by default. Tool schemas are introspected without calling the Google Maps API.

Reference

See PR #209 (UI5 MCP) for the expected output format. 15-20 minutes.

[KryptosAI]

Closing — Google Maps MCP needs a live API key to even list tools. Can't evaluate without a secret, and adding one just to hit an API-key-gated startup failure isn't useful.