Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ShubhenduVaid/flipbook/plugin install flipbookWrote 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/shubhenduvaid/flipbook/rec)<a href="https://agentmods.dev/mcp/shubhenduvaid/flipbook/rec"><img src="https://agentmods.dev/badge/mcp/shubhenduvaid/flipbook/rec.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
rec 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 4d 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
{
"rec": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/src/server.mjs"
],
"env": {
"FLIPBOOK_PLUGIN_ROOT": "${CLAUDE_PLUGIN_ROOT}"
}
}
}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.
- 4d ago First seen · 11 lines scan A e08a68d061e9
rec is an MCP server published in the GitHub repository ShubhenduVaid/flipbook (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
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
mochi
MCP server "mochi", hosted remotely at mochi.fast, as configured in khromov/codebay.
bun-docs
MCP server "bun-docs", hosted remotely at bun.com, as configured in khromov/codebay.
svelte
MCP server "svelte", hosted remotely at mcp.svelte.dev, as configured in khromov/codebay.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.