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/RudrenduPaul/DeskCert-CLIWrote 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/rudrendupaul/deskcert-cli/deskcert)<a href="https://agentmods.dev/mcp/rudrendupaul/deskcert-cli/deskcert"><img src="https://agentmods.dev/badge/mcp/rudrendupaul/deskcert-cli/deskcert/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/rudrendupaul/deskcert-cli/deskcert"><img src="https://agentmods.dev/badge/mcp/rudrendupaul/deskcert-cli/deskcert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deskcert 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
{
"deskcert": {
"command": "uvx",
"args": [
"deskcert-cli",
"deskcert-cli"
],
"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.
- 1mo ago First seen · 10 lines scan A f4682176dfdb
deskcert is an MCP server published in the GitHub repository RudrenduPaul/DeskCert-CLI (0 stars, last pushed 2d ago), licensed Apache-2.0. 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
uivision-mcp
MCP server for browser and desktop automation: OCR, image recognition, real mouse and keyboard input. Runs locally from the uivision-mcp-bridge npm package. Needs 1 environment variable to run.
pixelcheck
Real eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic. Runs locally from the pixelcheck npm package. Needs 1 environment variable to run.
mcp-vision-runtime
MCP server "mcp-vision-runtime" as configured in hussainn7/mcp-vision. Runs locally from the mcp-vision-runtime Python package.
ecobrowser
AI-native browser framework — the AI's hands and eyes on the web. Structured (no-pixel) perception, verified self-healing actions, incremental diff perception, a live view — as a TypeScript library and an MCP server. Runs locally from the ecobrowser npm package.
hermes-computer-use
Pixel-level browser automation MCP server for WSL2 — drive a real Chrome with screenshot + xdotool, no CDP. Runs locally from the hermes-computer-use Python package.
browser-use
Make websites accessible for AI agents. Runs locally from the browser-use Python package.