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/pour-picks-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/pour-picks-mcp/pour-picks)<a href="https://agentmods.dev/mcp/bguillow-rgb/pour-picks-mcp/pour-picks"><img src="https://agentmods.dev/badge/mcp/bguillow-rgb/pour-picks-mcp/pour-picks/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/pour-picks-mcp/pour-picks"><img src="https://agentmods.dev/badge/mcp/bguillow-rgb/pour-picks-mcp/pour-picks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pour-picks 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 11d 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
{
"pour-picks": {
"command": "npx",
"args": [
"-y",
"pour-picks-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.
- 11d ago First seen · 10 lines scan A af88d43ef54f
pour-picks is an MCP server published in the GitHub repository bguillow-rgb/pour-picks-mcp (0 stars, last pushed 4d 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
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.
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.
mcp-gateway-service
A token-efficient MCP gateway that provides one unified entry point for multiple downstream MCP services. Runs locally from the @jadchene/mcp-gateway-service npm package.
shotplan
MCP server "shotplan" as configured in lrvaka/shotplan. Runs locally from the shotplan-mcp Python package. Needs 3 environment variables to run.
registry
The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server. Remote server at mcpqueen.com.
agent-evidence
MCP server "agent-evidence" as configured in xiexie-qiuligao/agent-evidence-mcp. Launched with agent-evidence-mcp serve.