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/MarvinRey7879/patternfetch-clientWrote 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/marvinrey7879/patternfetch-client/patternfetch)<a href="https://agentmods.dev/mcp/marvinrey7879/patternfetch-client/patternfetch"><img src="https://agentmods.dev/badge/mcp/marvinrey7879/patternfetch-client/patternfetch/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/marvinrey7879/patternfetch-client/patternfetch"><img src="https://agentmods.dev/badge/mcp/marvinrey7879/patternfetch-client/patternfetch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
patternfetch 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
{
"patternfetch": {
"url": "https://patternfetch.com/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A 9072043bf30a
patternfetch is an MCP server published in the GitHub repository MarvinRey7879/patternfetch-client (0 stars, last pushed 3mo 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
robinhood-mcp
Robinhood Crypto Trading API for AI agents: quotes, holdings, orders read-only; opt-in trading. Runs locally from the robinhood-mcp npm package. Needs 4 environment variables to run.
trading-signals
Live AI crypto trading signals for agents. No API key needed to try — 3 signals + hit rate. Remote server at signals.x70.ai.
crypto-market-data
MCP server "crypto-market-data" as configured in nirholas/crypto-market-data. Runs locally from the crypto-market-data-mcp npm package. Needs 1 environment variable to run.
binance-mcp
MCP server for Binance exchange - spot trading, staking, wallet, NFT, pay, mining, and more. Runs locally from the @nirholas/binance-mcp-server npm package. Needs 2 environment variables to run.
finance-mcp
Live stock, crypto, SEC filings, insider trades, FX and macro data for LLM agents. Runs locally from the finance-data-mcp npm package. Needs 1 environment variable to run.
btc-node
Real BTC full node: fees, mempool, txs, portfolio, trace, whales, SEC, scraping, Reddit via x402. Remote server at mcp.btcnode.uk.