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/haljishi/vidwords-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/haljishi/vidwords-mcp/vidwords)<a href="https://agentmods.dev/mcp/haljishi/vidwords-mcp/vidwords"><img src="https://agentmods.dev/badge/mcp/haljishi/vidwords-mcp/vidwords/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/haljishi/vidwords-mcp/vidwords"><img src="https://agentmods.dev/badge/mcp/haljishi/vidwords-mcp/vidwords.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vidwords 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 16d 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
{
"vidwords": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://vidwords.com/mcp"
]
}
}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.
- 16d ago Changed · +1 lines 9af258b8ded4
- 1mo ago First seen · 9 lines scan A fe15080b21b9
vidwords is an MCP server published in the GitHub repository haljishi/vidwords-mcp (0 stars, last pushed 3d 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
weeek-mcp
Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools. Runs locally from the weeek-mcp npm package. Needs 6 environment variables to run.
mcp-knowledge-bridge
MCP server "mcp-knowledge-bridge" as configured in Brian20040323/mcp-knowledge-bridge. Runs locally from the mcp-knowledge-bridge Python package.
mcp
Manage tasks, sprints, projects, and wiki pages in your Ithura workspace. Runs locally from the ithura-mcp npm package. Needs 3 environment variables to run.
21st
MCP server "21st", hosted remotely at 21st.dev, as configured in 21st-dev/magic-mcp.
slack-mcp-server
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth. Runs locally from the @jtalk22/slack-mcp npm package. Needs 2 environment variables to run.
tailscale-mcp
Tailscale MCP server for managing your tailnet from AI assistants. Runs locally from the @yawlabs/tailscale-mcp npm package.