real_contract_for_ticker — PumpPill — token safety and measured outcomes MCP Prompt

real_contract_for_ticker is one of 2 prompts on the PumpPill — token safety and measured outcomes MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke real_contract_for_ticker from your client

• Claude Code PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker run in your project directory
• Claude Desktop PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker ~/.cursor/mcp.json
• VS Code PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker .vscode/mcp.json
• Zed PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker ~/.config/zed/settings.json
• Windsurf PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker ~/.codeium/windsurf/mcp_config.json
• Cline PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker ~/.gemini/settings.json
• Grok PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker .mcp.json (in your project root)
• ChatGPT PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker Settings → Connectors → Advanced → Developer mode
• Claude.ai PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker Settings → Connectors → Add custom connector
• LangChain PumpPill — token safety and measured outcomes Prompt/real_contract_for_ticker pip install langchain-mcp-adapters

Other prompts on this server

• check_before_buying

PumpPill — token safety and measured outcomes also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.