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/Wiplash-ai/wiplash-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/wiplash-ai/wiplash-mcp/wiplash)<a href="https://agentmods.dev/mcp/wiplash-ai/wiplash-mcp/wiplash"><img src="https://agentmods.dev/badge/mcp/wiplash-ai/wiplash-mcp/wiplash/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/wiplash-ai/wiplash-mcp/wiplash"><img src="https://agentmods.dev/badge/mcp/wiplash-ai/wiplash-mcp/wiplash.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wiplash 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
{
"wiplash": {
"url": "https://mcp.wiplash.ai/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.
- 12d ago First seen · 6 lines scan A 8ce38ff77125
wiplash is an MCP server published in the GitHub repository Wiplash-ai/wiplash-mcp (0 stars, last pushed 1mo 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
enquire-mcp
Long-term memory for AI agents — your Obsidian vault as searchable persistent memory. Runs locally from the @oomkapwn/enquire-mcp npm package.
sticker-mcp
MCP server "sticker-mcp" as configured in asashiki/sticker-mcp. Runs locally from the @asashiki/sticker-mcp npm package.
mcp-server
Project portfolio management for PMOs. Alternative to Microsoft Project Online. OAuth + PAT. Remote server at mcp.onplana.com.
discord-mcp
Safe Discord access for reading guild data and optionally managing bot messages. Runs locally from the @hypark5540/discord-mcp npm package. Needs 7 environment variables to run.
codex-mcp-bridge-for-chatgpt
MCP server "codex-mcp-bridge-for-chatgpt" as configured in menaje/codex-mcp-bridge-for-chatgpt. Runs locally from the codex-mcp-bridge-for-chatgpt npm package.
folderbridge-mcp
MCP server "folderbridge-mcp" as configured in MoonTzai/folderbridge-mcp. Runs locally from the folderbridge-mcp Python package.