vendors — Cisa Kev MCP Tool
vendors
(vendors) is one of 40 tools on the
Cisa Kev
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call vendors from your client
- Claude Code Cisa Kev vendors run in your project directory
- Claude Desktop Cisa Kev vendors ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cisa Kev vendors ~/.cursor/mcp.json
- VS Code Cisa Kev vendors .vscode/mcp.json
- Zed Cisa Kev vendors ~/.config/zed/settings.json
- Windsurf Cisa Kev vendors ~/.codeium/windsurf/mcp_config.json
- Cline Cisa Kev vendors ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cisa Kev vendors ~/.gemini/settings.json
- Grok Cisa Kev vendors .mcp.json (in your project root)
- ChatGPT Cisa Kev vendors Settings → Connectors → Advanced → Developer mode
- Claude.ai Cisa Kev vendors Settings → Connectors → Add custom connector
- LangChain Cisa Kev vendors pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cisa-kev https://gateway.pipeworx.io/cisa-kev/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- catalog
- entry
- recent
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.