gpufeed_status — VulnHunt Security Intelligence MCP Tool
gpufeed_status
(gpufeed status) is one of 11 tools on the
VulnHunt Security Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call gpufeed_status from your client
- Claude Code VulnHunt Security Intelligence gpufeed_status run in your project directory
- Claude Desktop VulnHunt Security Intelligence gpufeed_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VulnHunt Security Intelligence gpufeed_status ~/.cursor/mcp.json
- VS Code VulnHunt Security Intelligence gpufeed_status .vscode/mcp.json
- Zed VulnHunt Security Intelligence gpufeed_status ~/.config/zed/settings.json
- Windsurf VulnHunt Security Intelligence gpufeed_status ~/.codeium/windsurf/mcp_config.json
- Cline VulnHunt Security Intelligence gpufeed_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VulnHunt Security Intelligence gpufeed_status ~/.gemini/settings.json
- Grok VulnHunt Security Intelligence gpufeed_status .mcp.json (in your project root)
- ChatGPT VulnHunt Security Intelligence gpufeed_status Settings → Connectors → Advanced → Developer mode
- Claude.ai VulnHunt Security Intelligence gpufeed_status Settings → Connectors → Add custom connector
- LangChain VulnHunt Security Intelligence gpufeed_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vulnhunt https://vulnhunt-agent-api-production.up.railway.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.