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/nvdigitalsolutions/mcp-ai-wpoosWrote 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/nvdigitalsolutions/mcp-ai-wpoos/chatgpt-plugin-nvoos_site)<a href="https://agentmods.dev/mcp/nvdigitalsolutions/mcp-ai-wpoos/chatgpt-plugin-nvoos_site"><img src="https://agentmods.dev/badge/mcp/nvdigitalsolutions/mcp-ai-wpoos/chatgpt-plugin-nvoos_site/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/nvdigitalsolutions/mcp-ai-wpoos/chatgpt-plugin-nvoos_site"><img src="https://agentmods.dev/badge/mcp/nvdigitalsolutions/mcp-ai-wpoos/chatgpt-plugin-nvoos_site.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nvoos_site 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 15d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 15d ago First seen · 6 lines scan A d5b70ea9f9d3
nvoos_site is an MCP server published in the GitHub repository nvdigitalsolutions/mcp-ai-wpoos (7 stars, last pushed today), with no licence file. 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-10-06.
Other mcp servers, from other repositories
media-mcp
MCP server exposing Google Gemini media generation APIs as tools for AI agents. Runs locally from the media-mcp Python package.
raycast
Raycast workflow automation MCP server with 9 tools. Runs locally from the raycast-mcp-server npm package.
pm-copilot
MCP server "pm-copilot" as configured in dkships/pm-copilot. Runs dist/index.js with node.
a2aidentitytoll-mcp
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history. Remote server at a2aidentitytoll.clauxel.com.
computeruse
MCP server "computeruse" as configured in Konohamaru04/Computer-Use-Agent. Runs locally from the computeruse Python package.
lorem-forge-mcp
Generate placeholder text — lorem ipsum and alternatives. Runs locally from the lorem-forge-mcp npm package.