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/ByteOverDev/peak-window-mcp-appWrote 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/byteoverdev/peak-window-mcp-app/peak-window)<a href="https://agentmods.dev/mcp/byteoverdev/peak-window-mcp-app/peak-window"><img src="https://agentmods.dev/badge/mcp/byteoverdev/peak-window-mcp-app/peak-window/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/byteoverdev/peak-window-mcp-app/peak-window"><img src="https://agentmods.dev/badge/mcp/byteoverdev/peak-window-mcp-app/peak-window.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
peak-window 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
{
"peak-window": {
"command": "npx",
"args": [
"-y",
"peak-window"
],
"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.
- 1mo ago First seen · 10 lines scan A 247afbf258e1
peak-window is an MCP server published in the GitHub repository ByteOverDev/peak-window-mcp-app (3 stars, last pushed 4mo 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
sipcode
Sip your tokens, don't gulp them. Keep Claude Code's context clean: drift detection, re-read dedup, integrity scoring, AST-aware reads, and 15 MCP tools for Claude Desktop. Runs locally from the sipcode npm package.
google-search-console-mcp
MCP server for Google Search Console: query performance data, inspect URLs, check indexing, and generate HTML SEO audit reports from Claude, Cursor, Zed, and any Model Context Protocol client. Runs locally from the mcp-google-search-console Python package. Needs 6 environment variables to run.
smart-connections-mcp
Local semantic search over Obsidian vaults via Smart Connections embeddings. Multi-vault, private. Runs locally from the smart-connections-mcp npm package. Needs 1 environment variable to run.
lorg-mcp-server
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP. Runs locally from the lorg-mcp-server npm package. Needs 1 environment variable to run.
laserfiche-mcp
Model Context Protocol (MCP) server for self-hosted Laserfiche repositories — search and read documents from Claude. Runs locally from the laserfiche-mcp Python package. Needs 6 environment variables to run.
mcp
Search and post remote jobs, browse companies, check salaries, and find talent on Himalayas.app. Remote server at mcp.himalayas.app.