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/peteretelej/md-serverWrote 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/peteretelej/md-server/md-server)<a href="https://agentmods.dev/mcp/peteretelej/md-server/md-server"><img src="https://agentmods.dev/badge/mcp/peteretelej/md-server/md-server/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/peteretelej/md-server/md-server"><img src="https://agentmods.dev/badge/mcp/peteretelej/md-server/md-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
md-server 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
{ "md-server": { "command": "uvx", "args": [ "md-server" ] } }
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 802b40e8f883
md-server is an MCP server published in the GitHub repository peteretelej/md-server (3 stars, last pushed 7mo 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
mcp-server-excel
MCP server "mcp-server-excel" as configured in sbroenne/mcp-server-excel. Launched with Sbroenne.ExcelMcp.McpServer.
adeu
MCP server "adeu" as configured in dealfluence/adeu. Runs locally from the adeu-server Python package.
biligWorkpaperFile
MCP server "biligWorkpaperFile" as configured in proompteng/bilig. Launched with npm exec --yes --package @bilig/workpaper@latest -- bilig-workpaper-mcp --workpa.
docspace
MCP server "docspace" as configured in ONLYOFFICE/docspace-mcp. Launched with https://github.com/ONLYOFFICE/docspace-mcp/releases/download/v3.2.0/onlyoffice-d. Needs 2 environment variables to run.
bilig-workpaper
Formula-backed WorkPaper tools for workbook readback, input edits, and JSON persistence. Runs locally from the @bilig/workpaper npm package.
logisheets-mcp
An Excel-compatible spreadsheet engine for agents: deterministic formulas, block memory, real .xlsx. Runs locally from the logisheets-mcp npm package. Needs 1 environment variable to run.