run_stack — MarketPing MCP Tool Mutating
run_stack
(run stack) is one of 24 tools on the
MarketPing
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_stack from your client
- Claude Code MarketPing run_stack run in your project directory
- Claude Desktop MarketPing run_stack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MarketPing run_stack ~/.cursor/mcp.json
- VS Code MarketPing run_stack .vscode/mcp.json
- Zed MarketPing run_stack ~/.config/zed/settings.json
- Windsurf MarketPing run_stack ~/.codeium/windsurf/mcp_config.json
- Cline MarketPing run_stack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MarketPing run_stack ~/.gemini/settings.json
- Grok MarketPing run_stack .mcp.json (in your project root)
- ChatGPT MarketPing run_stack Settings → Connectors → Advanced → Developer mode
- Claude.ai MarketPing run_stack Settings → Connectors → Add custom connector
- LangChain MarketPing run_stack pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marketping https://mcp.marketping.in/mcpOther tools on this server
- search
- fetch
- resolve_company
- company_snapshot
- recent_alerts
- alert_reaction
- search_filings
- list_documents
- doc_contents
- read_pages
- audit_report
- screener_fields
- run_screener
- ipo_pipeline
- fpi_flows
- results_calendar
- daily_briefing
- list_stacks
- stack_changes
- list_models
- run_model
- watchlist_list
- watchlist_add
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.