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.svg" alt="Measured on agentmods" 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 today.
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.
- today First seen · 9 lines scan A bbd201034b30
fetch is an MCP server published in the GitHub repository lirantal/ls-mcp (84 stars, last pushed today), 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
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.
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.
viraill-mcp
MCP server "viraill-mcp" as configured in crypto-yannso/viraill-mcp. Runs locally from the @crypto-yannso/viraill-mcp npm package.
google-workspace-mcp
MCP server for Google Workspace: Docs, Sheets, Drive, Gmail, Calendar, Slides, and Forms. Runs locally from the google-workspace-mcp npm package.
tg-mcp
Local MCP server for your Telegram personal account — channels, digests, messaging, folders and more. Runs locally from the tg-mcp npm package.
omni-mcp-server
All-in-one MCP server: GitHub, Git, Slack, web fetch, memory, and filesystem. Agent Mode opt-in. Runs locally from the @bitofacoder/omni-mcp-server npm package. Needs 3 environment variables to run.