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/novadyne-hq/vulnfeed-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/novadyne-hq/vulnfeed-mcp/vulnfeed)<a href="https://agentmods.dev/mcp/novadyne-hq/vulnfeed-mcp/vulnfeed"><img src="https://agentmods.dev/badge/mcp/novadyne-hq/vulnfeed-mcp/vulnfeed/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/novadyne-hq/vulnfeed-mcp/vulnfeed"><img src="https://agentmods.dev/badge/mcp/novadyne-hq/vulnfeed-mcp/vulnfeed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vulnfeed 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 11d 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
{
"vulnfeed": {
"command": "uvx",
"args": [
"vulnfeed-mcp"
],
"env": {
"VULNFEED_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.
- 11d ago First seen · 11 lines scan A 0dbd0b8fe9e6
vulnfeed is an MCP server published in the GitHub repository novadyne-hq/vulnfeed-mcp (1 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-08-31.
Other mcp servers, from other repositories
tollbooth
Token swaps and honeypot/rug checks for AI agents on 8 chains, paid per-call in USDC via x402. Runs locally from the tollboothswap-mcp npm package. Needs 2 environment variables to run.
m2mcent
Ultra-lightweight x402 payment wrapper for AI Agents and MCP Servers. Monetize any API in 3 lines of code. Runs locally from the m2mcent-sdk npm package. Needs 3 environment variables to run.
purify-feeds-mcp
MCP server "purify-feeds-mcp" as configured in eason4kim-rocket/purify-feeds-mcp. Runs in Docker (ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1). Needs 2 environment variables to run.
patch-tuesday
MCP server for Microsoft Patch Tuesday security updates (MSRC Security Update Guide). Runs locally from the patch-tuesday-mcp Python package.
vulnerability-mcp-server
MCP server "vulnerability-mcp-server" as configured in CedricG-dev/nvd-mcp. Runs locally from the vulnerability-mcp-server Python package.
x402-mcp-server
x402 Payment Gateway for AI Agents — enable micropayments between agents using USDC on Solana. Runs locally from the x402-mcp-server Python package.