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/lightpaperorg/lightpaperWrote 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/lightpaperorg/lightpaper/lightpaper-mcp)<a href="https://agentmods.dev/mcp/lightpaperorg/lightpaper/lightpaper-mcp"><img src="https://agentmods.dev/badge/mcp/lightpaperorg/lightpaper/lightpaper-mcp/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/lightpaperorg/lightpaper/lightpaper-mcp"><img src="https://agentmods.dev/badge/mcp/lightpaperorg/lightpaper/lightpaper-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lightpaper-mcp 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
{
"lightpaper-mcp": {
"command": "uvx",
"args": [
"lightpaper-mcp"
],
"env": {
"LIGHTPAPER_API_KEY": "",
"LIGHTPAPER_BASE_URL": ""
}
}
}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 · 12 lines scan A 6f1d2e8750de
lightpaper-mcp is an MCP server published in the GitHub repository lightpaperorg/lightpaper (0 stars, last pushed 3mo 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
caelune-mcp
MCP server "caelune-mcp" as configured in EllisMorrow/Caelune. Launched with https://github.com/EllisMorrow/Caelune/releases/download/v0.5.6/caelune-mcp-win-.
fetchv2-mcp-server
A robust MCP server for fetching and extracting web content using Trafilatura. Runs locally from the fetchv2-mcp-server Python package.
markdown
MCP server "markdown", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-markdown.
lyrenth-mcp
Read any public web page as a clean AIDocument (Markdown + structure) through Lyrenth. Runs locally from the lyrenth-mcp npm package.
abovo-mcp-server
MCP server "abovo-mcp-server" as configured in seanfenlon/abovo-mcp-server. Launched with https://github.com/seanfenlon/abovo-mcp-server/releases/download/v1.1.1/abovo-mc. Needs 5 environment variables to run.
notion-mcp
Notion MCP server — search, export, and import pages as markdown. Runs locally from the @shck-dev/notion-mcp npm package. Needs 3 environment variables to run.