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/Cubenest/rrweb-stackInstalling this writes the configuration, not the program: `${CLAUDE_PROJECT_DIR:-.}/node_modules/.bin/tsx` has to be on your PATH already, or the server will not start.
Wrote 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/cubenest/rrweb-stack/peek-dev-src)<a href="https://agentmods.dev/mcp/cubenest/rrweb-stack/peek-dev-src"><img src="https://agentmods.dev/badge/mcp/cubenest/rrweb-stack/peek-dev-src/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/cubenest/rrweb-stack/peek-dev-src"><img src="https://agentmods.dev/badge/mcp/cubenest/rrweb-stack/peek-dev-src.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
peek-dev-src 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
{
"peek-dev-src": {
"command": "${CLAUDE_PROJECT_DIR:-.}/node_modules/.bin/tsx",
"args": [
"${CLAUDE_PROJECT_DIR:-.}/packages/peek-mcp/src/index.ts"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 8 lines scan A eed04783ee16
peek-dev-src is an MCP server published in the GitHub repository Cubenest/rrweb-stack (8 stars, last pushed 3mo ago), licensed Apache-2.0. 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
qaskills
Search, inspect, and install 400+ QA testing skills from qaskills.sh into any MCP client. Runs locally from the @qaskills/mcp npm package. Needs 1 environment variable to run.
plumb-mcp
Figma → code MCP: no rate limits, no metered quotas, verification loop. Works on every Figma plan. Runs locally from the plumb-mcp npm package. Needs 2 environment variables to run.
browseweave
Secure local browser bridge and MCP server for AI clients. Runs locally from the browseweave npm package.
annotation-overlay-mcp
MCP server "annotation-overlay-mcp" as configured in cc10143/annotation-overlay-mcp. Runs locally from the annotation-overlay-mcp npm package.
alive-analysis
Query alive-analysis history from any AI client. Tools: list, get, search, dashboard export. Runs locally from the alive-analysis-mcp npm package. Needs 1 environment variable to run.
cgraphy
Code knowledge graph over MCP: compact, token-budgeted context for AI coding agents. Runs locally from the cgraphy Python package.