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/printyourduck/printyourduck-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/printyourduck/printyourduck-mcp/quote)<a href="https://agentmods.dev/mcp/printyourduck/printyourduck-mcp/quote"><img src="https://agentmods.dev/badge/mcp/printyourduck/printyourduck-mcp/quote/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/printyourduck/printyourduck-mcp/quote"><img src="https://agentmods.dev/badge/mcp/printyourduck/printyourduck-mcp/quote.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
quote 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 8d 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
{
"quote": {
"command": "npx",
"args": [
"-y",
"@printyourduck/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.
- 8d ago First seen · 10 lines scan A 2a404464538c
quote is an MCP server published in the GitHub repository printyourduck/printyourduck-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
merchant-catalog-mcp
MCP server "merchant-catalog-mcp" as configured in Thethirdone3/merchant-catalog-mcp. Runs locally from the merchant-catalog-mcp npm package.
codex-control-plane-mcp
Durable MCP control plane for long-running Codex Desktop tasks. Runs locally from the codex-control-plane-mcp Python package.
vinted-client
CLI and MCP server for the Vinted marketplace — search, items, sellers, price compare, trending. Runs locally from the @googlarz/vinted-client npm package.
datalens
MCP server "datalens" as configured in ADIKANT/datalens-dev-mcp. Launched with datalens-dev-mcp stdio.
mcp-server
Agent-native global eSIM: buy for 193 countries, per-MB in USDT/USDC. Agents earn 20% referral. Runs locally from the @roamzy/mcp-server npm package. Needs 3 environment variables to run.
chestnyznak-mcp
A local connector for the Chestniy ZNAK API, a Russian system used to verify product marking codes. It runs through the Chestniy ZNAK MCP server and requires an API key environment variable.