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/oscardvs/zoteusWrote 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/oscardvs/zoteus/zoteus-zoteus)<a href="https://agentmods.dev/mcp/oscardvs/zoteus/zoteus-zoteus"><img src="https://agentmods.dev/badge/mcp/oscardvs/zoteus/zoteus-zoteus/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/oscardvs/zoteus/zoteus-zoteus"><img src="https://agentmods.dev/badge/mcp/oscardvs/zoteus/zoteus-zoteus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zoteus 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.
What it actually says
{
"zoteus": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@oscardvs/[email protected]"
],
"env": {
"ZOTERO_API_KEY": "${user_config.zotero_api_key}"
}
}
}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 Changed 88b2d1c35fa6
- 18d ago Changed c9a62c6b1e13
- 19d ago Changed b189729399d4
- 22d ago First seen · 13 lines scan A 3802f34d63f9
zoteus is an MCP server published in the GitHub repository oscardvs/zoteus (61 stars, last pushed yesterday), 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-09-28.
Other mcp servers, from other repositories
reportflow-mcp
Generate PDF reports from Re:port Flow templates via Claude and other AI agents. Runs locally from the reportflow-mcp npm package. Needs 4 environment variables to run.
sheetrender-mcp
Render PDFs from templates and spreadsheet data via SheetRender, locally or at mcp.sheetrender.com. Runs locally from the @sheetrender/mcp npm package. Needs 2 environment variables to run.
truepath-pdf-mcp
Local-only PDF tools for AI — extract text, search, split/merge, render pages. Files never leave. Runs locally from the @truepathpdf/mcp-server npm package.
pdf-it
Native PDF renderer for AI markdown. Cover, TOC, page-numbered footer. Fonts embedded, zero config. Runs locally from the pdf-it-mcp npm package.
customjs-mcp
Host static HTML pages, generate PDFs, screenshots, scrape JS sites, run sandboxed JavaScript. Remote server at mcp.customjs.space.
parse
Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells. Runs locally from the @ailang/parse npm package. Needs 2 environment variables to run.