Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/cablate/mcp-google-mapWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/cablate/mcp-google-map/google-map)<a href="https://agentmods.dev/mcp/cablate/mcp-google-map/google-map"><img src="https://agentmods.dev/badge/mcp/cablate/mcp-google-map/google-map/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/cablate/mcp-google-map/google-map"><img src="https://agentmods.dev/badge/mcp/cablate/mcp-google-map/google-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
google-map scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"google-map": {
"command": "npx",
"args": [
"-y",
"@cablate/mcp-google-map"
],
"env": {
"GOOGLE_MAPS_API_KEY": "",
"GOOGLE_MAPS_ENABLED_TOOLS": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A 7cc691953859
google-map is an MCP server published in the GitHub repository cablate/mcp-google-map (470 stars, last pushed 20d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
xquik
MCP server "xquik", hosted remotely at xquik.com, as configured in Xquik-dev/x-twitter-scraper.
openstreetmap-mcp-server
Geocode, reverse geocode, and run Overpass spatial queries on OpenStreetMap data. Runs locally from the @cyanheads/openstreetmap-mcp-server npm package. Needs 6 environment variables to run.
kolmopdf
MCP server for KolmoPDF — PDF parsing, layout-preserving translation, and Markdown format conversion. Runs locally from the @kolmopdf/mcp-server npm package. Needs 1 environment variable to run.
osm-mcp
Geocoding, walking/driving/cycling distances, route optimization, isochrones and POI search on OSM. Runs locally from the osm-mcp npm package. Needs 4 environment variables to run.
ultraprospect
MCP server "ultraprospect" as configured in maxgfr/ultraprospect. Runs locally from the ultraprospect npm package.
xrocket
MCP server "xrocket" as configured in nakazanie-ton/myrocket. Runs ${PLUGIN_ROOT}/dist/cli.js with node. Needs 6 environment variables to run.