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/Sergiorushy326/google-flow-mcpWrote 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/sergiorushy326/google-flow-mcp/google-flow-mcp-server)<a href="https://agentmods.dev/mcp/sergiorushy326/google-flow-mcp/google-flow-mcp-server"><img src="https://agentmods.dev/badge/mcp/sergiorushy326/google-flow-mcp/google-flow-mcp-server/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/sergiorushy326/google-flow-mcp/google-flow-mcp-server"><img src="https://agentmods.dev/badge/mcp/sergiorushy326/google-flow-mcp/google-flow-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
google-flow-mcp-server 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 9d 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-flow-mcp-server": { "command": "npx", "args": [ "-y", "google-flow-mcp-server" ] } }
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.
- 9d ago First seen · 9 lines scan A 6e74f372486a
google-flow-mcp-server is an MCP server published in the GitHub repository Sergiorushy326/google-flow-mcp (0 stars, last pushed 2d 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-31.
Other mcp servers, from other repositories
directory
Quality-ranked, cross-platform directory of AI coding skills, plugins and MCP servers. Remote server at skills.911fund.io.
mcp-office-excel
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 4 environment variables to run.
macbeth
MCP server "macbeth" as configured in wende/macbeth. Runs client/dist/mcp.js with node.
mcp
Schedule and publish social posts to 11 platforms with media, campaigns, analytics and AI captions. Runs locally from the @posteverywhere/mcp npm package. Needs 1 environment variable to run.
picassoweb
PicassoWeb — MCP server that turns any website into a faithful replication kit: design tokens, real assets, animations, layout trees, section clones, screenshots, and pixel-diff verification. Runs locally from the picassoweb npm package.
computeruse
MCP server "computeruse" as configured in Konohamaru04/Computer-Use-Agent. Runs locally from the computeruse Python package.