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/lirantal/ls-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/lirantal/ls-mcp/fetch)<a href="https://agentmods.dev/mcp/lirantal/ls-mcp/fetch"><img src="https://agentmods.dev/badge/mcp/lirantal/ls-mcp/fetch/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/lirantal/ls-mcp/fetch"><img src="https://agentmods.dev/badge/mcp/lirantal/ls-mcp/fetch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
fetch 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- fetch — 100% identical, 0 lines differ
What it actually says
{
"fetch": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 2. 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 · 9 lines scan A bbd201034b30
fetch is an MCP server published in the GitHub repository lirantal/ls-mcp (84 stars, last pushed 17d 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-09-07.
Other mcp servers, from other repositories
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
fast-mcp-telegram
Multi-tenant Telegram gateway for AI agents — HTTP+stdio transport, 8 agent-optimized tools, MTProto User API. Runs locally from the fast-mcp-telegram Python package. Needs 4 environment variables to run.
telegram-dev
MCP server "telegram-dev" as configured in leshchenko1979/fast-mcp-telegram. Runs src.server with python3.
linkedin-mcp-server
Human-in-the-loop LinkedIn outreach and a built-in sales CRM for AI agents. Safety-gated, anti-spam. Remote server at app.salesbot.cz.
salesbot
MCP server "salesbot", hosted remotely at app.salesbot.cz, as configured in Kubis010/linkedin-mcp-server-salesbot.
uap-pulse
Search and map the Pentagon UAP/UFO releases plus curated official archives from 12 nations. Runs locally from the uap-pulse npm package.