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/pawvej/vidgridWrote 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/pawvej/vidgrid/vidgrid)<a href="https://agentmods.dev/mcp/pawvej/vidgrid/vidgrid"><img src="https://agentmods.dev/badge/mcp/pawvej/vidgrid/vidgrid/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/pawvej/vidgrid/vidgrid"><img src="https://agentmods.dev/badge/mcp/pawvej/vidgrid/vidgrid.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
vidgrid 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 29d 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
{ "vidgrid": { "command": "uvx", "args": [ "vidgrid-mcp" ], "env": { "VIDGRID_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.
- 29d ago First seen · 11 lines scan A dca7ed0d2b28
vidgrid is an MCP server published in the GitHub repository pawvej/vidgrid (0 stars, last pushed 1mo 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-09-29.
Other mcp servers, from other repositories
video-agent-runtime
MCP server "video-agent-runtime" as configured in YansIlinta/video-agent-runtime. Runs locally from the video-agent-runtime npm package.
prometheus-mcp-server
MCP server "prometheus-mcp-server" as configured in pab1it0/prometheus-mcp-server. Runs in Docker (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2). Needs 14 environment variables to run.
servicenow
MCP server "servicenow" as configured in serac-labs/serac. Runs locally from the servicenow-mcp-stdio npm package.
seekstone
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax. Runs locally from the seekstone npm package. Needs 1 environment variable to run.
aiterm-mcp
Persistent terminals and one launcher for Claude, Codex, Grok, and Cursor harnesses. Runs locally from the aiterm-mcp npm package.
swiss-transport-mcp
MCP server for Swiss public transport – OJP journey planner, real-time departures, disruptions, occupancy, ticket prices, train formations and open data from opentransportdata.swiss. Runs locally from the swiss-transport-mcp Python package.