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/yooumuu/parsejet-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/yooumuu/parsejet-mcp/mcp-server)<a href="https://agentmods.dev/mcp/yooumuu/parsejet-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/yooumuu/parsejet-mcp/mcp-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/yooumuu/parsejet-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/yooumuu/parsejet-mcp/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-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
{ "mcp-server": { "command": "npx", "args": [ "-y", "@parsejet/mcp-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 · 9 lines scan A 228867a3a83c
mcp-server is an MCP server published in the GitHub repository yooumuu/parsejet-mcp (0 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
upapi-mcp
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more. Runs locally from the @upapi/mcp npm package. Needs 2 environment variables to run.
alidocs-web-mcp
Local MCP bridge that exposes the DingTalk Doc (alidocs) page already open in your browser to any MCP host over stdio. Runs locally from the @magical-index/alidocs-web-mcp npm package.
screenshot-pdf
Capture screenshots (PNG/JPEG/WebP) and generate PDFs from any URL. x402 payments. Remote server at screenshot-pdf.api.klymax402.com.
snapforge
Screenshots, PDFs and Markdown from any URL or HTML for AI agents, via the SnapForge API. Runs locally from the snapforge-mcp npm package. Needs 1 environment variable to run.
pagewatch
Read a URL as clean markdown, screenshot a website, url to PDF. Web access for agents, no signup. Runs locally from the pagewatch-mcp npm package. Needs 2 environment variables to run.
customjs-mcp
Host static HTML pages, generate PDFs, screenshots, scrape JS sites, run sandboxed JavaScript. Remote server at mcp.customjs.space.