Vulnfeed MCP vs Scrivener MCP
A side-by-side look at the Vulnfeed MCP and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vulnfeed MCP for security work as a local process; choose Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vulnfeed MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
VULNFEED_API_KEY. - You want tools like
scan_project, scan_lockfile, check_package.
Choose Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Knowledge & Memory |
| Quality signal | 57/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | VULNFEED_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 67 |
| Directory activity | 3 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Vulnfeed MCP | View Scrivener MCP |
Tools & capabilities
Vulnfeed MCP tools 10
scan_projectAuto-detect and scan all lockfiles in a directoryscan_lockfileScan a specific lockfilecheck_packageCheck a single package for vulnerabilitieslookup_cveDetailed CVE info with EPSS + fix versions (license key or x402)monitor_projectRegister for continuous monitoring (optional `webhook_url` for push alerts)check_alertsNew vulns since last scanset_webhookSet, rotate or remove a project's webhookupdate_depsUpdate snapshot after upgrading packageslist_monitoredSee all monitored projectsunmonitor_projectRemove from monitoring
Scrivener MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Vulnfeed MCP
{
"mcpServers": {
"infai-tech-vulnfeed-mcp": {
"command": "uvx",
"args": [
"vulnfeed-mcp"
],
"env": {
"VULNFEED_API_KEY": "YOUR_VULNFEED_API_KEY_HERE"
}
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
Vulnfeed MCP is categorized under Security and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Vulnfeed MCP for security work and Scrivener MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Vulnfeed MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Scrivener MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add infai-tech-vulnfeed-mcp and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vulnfeed MCP has a quality signal of 57/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.
