recall — Nci Evs MCP Tool
recall
(recall) is one of 40 tools on the
Nci Evs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call recall from your client
- Claude Code Nci Evs recall run in your project directory
- Claude Desktop Nci Evs recall ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nci Evs recall ~/.cursor/mcp.json
- VS Code Nci Evs recall .vscode/mcp.json
- Zed Nci Evs recall ~/.config/zed/settings.json
- Windsurf Nci Evs recall ~/.codeium/windsurf/mcp_config.json
- Cline Nci Evs recall ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nci Evs recall ~/.gemini/settings.json
- Grok Nci Evs recall .mcp.json (in your project root)
- ChatGPT Nci Evs recall Settings → Connectors → Advanced → Developer mode
- Claude.ai Nci Evs recall Settings → Connectors → Add custom connector
- LangChain Nci Evs recall pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nci-evs https://gateway.pipeworx.io/nci-evs/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
- forget
- evs_search_concepts
- evs_concept
- evs_terminologies
- evs_concept_relations
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.