insider_activity — filingpulse MCP Prompt

insider_activity is one of 3 prompts on the filingpulse MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke insider_activity from your client

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

Other prompts on this server

• events_digest
• ipo_pipeline

filingpulse also offers 2 resources — 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.