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/bguillow-rgb/percolate-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/bguillow-rgb/percolate-mcp/percolate)<a href="https://agentmods.dev/mcp/bguillow-rgb/percolate-mcp/percolate"><img src="https://agentmods.dev/badge/mcp/bguillow-rgb/percolate-mcp/percolate/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/bguillow-rgb/percolate-mcp/percolate"><img src="https://agentmods.dev/badge/mcp/bguillow-rgb/percolate-mcp/percolate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
percolate 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 12d 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
{
"percolate": {
"command": "npx",
"args": [
"-y",
"percolate-mcp"
],
"env": {}
}
}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.
- 12d ago First seen · 10 lines scan A 101e8f43119d
percolate is an MCP server published in the GitHub repository bguillow-rgb/percolate-mcp (0 stars, last pushed 5d 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
selat
The unified tool gateway for AI agents: one credential, every upstream, over MCP and REST. Runs locally from the @fajarhide/selat npm package.
dsh-continuity
Asset consistency and output verification for agent-generated game media: image, voice, music and SFX from local Vulkan backends with zero VRAM when idle, or from any OpenAI-shaped image/ASR API instead. Runs locally from the dsh-continuity Python package.
local-gpu-imagegen
MCP server "local-gpu-imagegen" as configured in ChevalGrand520/local-gpu-imagegen. Runs scripts/mcp_server.py with python.
perfume-picks
Search the Perfume Picks fragrance database: 13,000+ scents with notes, dupes, and wear data. Runs locally from the perfume-picks-mcp npm package.
pour-picks
Search the Pour Picks bourbon & whiskey database: 4,700+ bottles with tasting profiles and prices. Runs locally from the pour-picks-mcp npm package.
ollama-web-search
MCP stdio server exposing Ollama's hosted web search and web fetch APIs as tools for any MCP client. Runs locally from the ollama-web-search Python package.