screen_by_tickers — simplefunctions MCP Tool
screen_by_tickers
(screen by tickers) is one of 108 tools on the
simplefunctions
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call screen_by_tickers from your client
- Claude Code simplefunctions screen_by_tickers run in your project directory
- Claude Desktop simplefunctions screen_by_tickers ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor simplefunctions screen_by_tickers ~/.cursor/mcp.json
- VS Code simplefunctions screen_by_tickers .vscode/mcp.json
- Zed simplefunctions screen_by_tickers ~/.config/zed/settings.json
- Windsurf simplefunctions screen_by_tickers ~/.codeium/windsurf/mcp_config.json
- Cline simplefunctions screen_by_tickers ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI simplefunctions screen_by_tickers ~/.gemini/settings.json
- Grok simplefunctions screen_by_tickers .mcp.json (in your project root)
- ChatGPT simplefunctions screen_by_tickers Settings → Connectors → Advanced → Developer mode
- Claude.ai simplefunctions screen_by_tickers Settings → Connectors → Add custom connector
- LangChain simplefunctions screen_by_tickers pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http simplefunctions https://simplefunctions.dev/api/mcp/mcpOther tools on this server
- get_context
- list_theses
- inject_signal
- trigger_evaluation
- scan_markets
- create_thesis
- explore_public
- get_markets
- query_databento
- query
- screen_markets
- create_strategy
- list_strategies
- update_strategy
- get_milestones
- get_forecast
- get_settlements
- get_balance
- get_orders
- get_schedule
- get_fills
- what_if
- augment_tree
- get_edges
- get_trade_ideas
- create_intent
- list_intents
- cancel_intent
- search_x
- x_volume
- x_news
- x_account
- configure_heartbeat
- update_thesis
- add_position
- update_position
- close_position
- get_evaluation_history
- update_nodes
- get_heartbeat_status
- monitor_the_situation
- enrich_content
- create_skill
- list_skills
- run_skill
- publish_skill
- fork_skill
- browse_public_skills
- fork_thesis
- get_world_state
- get_world_delta
- read_forum
- post_to_forum
- subscribe_forum
- query_gov
- query_econ
- legislation
- inspect_ticker
- get_market_detail
- get_market_history
- get_market_microstructure_history
- batch_markets
- get_market_index
- get_index_history
- get_regime_scan
- get_contagion
- get_market_diff
- get_highlights
- get_briefing
- get_calendar
- get_economic_anchors
- get_yield_curves
- get_yield_curve
- get_newmarkets
- get_calibration
- get_answer
- get_agent_guide
- site_search
- get_changes
- get_skills
- get_public_skill
- list_glossary
- get_glossary_term
- list_opinions
- get_opinion
- list_technicals
- get_technical
- list_legislation
- list_congress_members
- get_congress_member
- get_feed
- get_changes_delta
- list_forum_channels
- get_positions
- portfolio_positions_list
- portfolio_ledger_list
- portfolio_fills_list
- portfolio_attribution_daily
- portfolio_attribution_grouped
- portfolio_risk_get
- portfolio_activity_list
- get_thesis_context
- tts
- stt
- explore_theses
- get_heartbeat_config
- get_legislation
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.