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/btitkin/OwlynMCPWrote 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/btitkin/owlynmcp/owlyn-mcp)<a href="https://agentmods.dev/mcp/btitkin/owlynmcp/owlyn-mcp"><img src="https://agentmods.dev/badge/mcp/btitkin/owlynmcp/owlyn-mcp/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/btitkin/owlynmcp/owlyn-mcp"><img src="https://agentmods.dev/badge/mcp/btitkin/owlynmcp/owlyn-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
owlyn-mcp 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aza-mcp — 86% identical, 4 lines differ
What it actually says
{ "owlyn-mcp": { "command": "npx", "args": [ "-y", "owlyn-mcp" ] } }
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.
- 9d ago First seen · 9 lines scan A 03256a827610
owlyn-mcp is an MCP server published in the GitHub repository btitkin/OwlynMCP (1 stars, last pushed 2mo 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
reporelay
Bounded local MCP access to one approved repository for AI read/search and structured handoffs. Runs locally from the reporelay-mcp npm package.
ellmos-controlcenter-mcp
MCP control plane: local server discovery, profiles, capability bundles, and policy audits. Runs locally from the ellmos-controlcenter-mcp npm package.
grape
MCP server "grape" as configured in gael55x/Grape. Launched with grape mcp --stdio.
repogrammar
Local implementation-pattern context for coding agents. Runs locally from the @sioyooo/repogrammar npm package.
mcp-light-memory
MCP server "mcp-light-memory" as configured in PeterPirog/mcp-light-memory. Launched with https://github.com/PeterPirog/mcp-light-memory/releases/download/v1.8.1/mcp-ligh.
ctxd
MCP server "ctxd" as configured in g0GobliN/ctxd. Runs packages/cli/dist/index.js with node.