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/veldica/publishready-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/veldica/publishready-mcp/publishready)<a href="https://agentmods.dev/mcp/veldica/publishready-mcp/publishready"><img src="https://agentmods.dev/badge/mcp/veldica/publishready-mcp/publishready/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/veldica/publishready-mcp/publishready"><img src="https://agentmods.dev/badge/mcp/veldica/publishready-mcp/publishready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
publishready 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 12d 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
{
"publishready": {
"command": "npx",
"args": [
"-y",
"@veldica/publishready-mcp"
],
"env": {}
}
}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.
- 12d ago First seen · 10 lines scan A 3dfe09661cdc
publishready is an MCP server published in the GitHub repository veldica/publishready-mcp (2 stars, last pushed 4mo 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
video-extract-mcp
Download any video from a URL, or get its transcript and key frames. All local, no API keys. Runs locally from the @yanlinglabs/video-extract-mcp npm package. Needs 3 environment variables to run.
cairn
MCP server exposing Cairn's local-first file-organization tools to Claude Code, Codex, Cursor, and any MCP client. Runs locally from the cairn-mcp-server Python package. Needs 1 environment variable to run.
vector-mirror
Deterministic SVG perception for LLM agents — measures, never guesses. MCP server. Runs locally from the vector-mirror npm package.
desktopcommanderpy
MCP server "desktopcommanderpy" as configured in eduardoddddddd/DesktopCommanderPy. Runs locally from the desktopcommanderpy Python package.
openflowkit-mcp
Local-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. Runs locally from the @vrun-design/openflowkit-mcp npm package.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.