ShareSeer offers an MCP server that exposes access to SEC filings, insider transactions, and market-wide data via Claude and other MCP-compatible assistants. This server is accessed remotely through a single HTTP-based integration URL that includes your API key. After configuring the MCP client with the remote endpoint, you can query a range of tools such as get_company_filings, get_insider_transactions, get_recent_filings, get_recent_insider_activity, get_largest_daily_transactions, and get_largest_weekly_transactions. Use natural language prompts or structured tool calls to retrieve filings for a specific company, inspect insider activity, or explore market-wide data and largest transactions. The platform handles authentication via your API key and enforces subscription-based rate limits and data history windows according to your plan.

Prerequisites:

• Python 3.8+ installed on the host
• Access to the internet from the host
• A valid ShareSeer API key (starts with sk-shareseer-)

1. Create a Python environment (recommended): python3 -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate

2. Install the MCP server package (if provided as a module/package): pip install shareseer-mcp-server # Replace with the actual package name if different

3. Configure your environment with your API key: export SHARESEER_API_KEY=sk-shareseer-xxxxxxxx

   On Windows PowerShell: $env:SHARESEER_API_KEY = 'sk-shareseer-xxxxxxxx'

4. Run the MCP server module: python -m shareseer_mcp_server

5. Point your MCP client (e.g., Claude integration) to the remote URL and pass your API key as a parameter in the URL: https://shareseer.com/mcp?api_key=YOUR_API_KEY_HERE

6. Verify you can access the available tools by issuing a test query through your MCP client.

Notes:

• If you’re hosting locally, ensure the port used by the MCP server is accessible to your clients.
• Manage your API key securely and rotate it per your security policy.

Tips and common issues:

• Ensure your API key is active and starts with sk-shareseer-; invalid keys will trigger authentication errors.
• When using rate-limited plans, stagger requests across time to avoid hitting limits; consider upgrading for higher quotas.
• The MCP server supports tool discovery; if a tool is unavailable, verify your subscription tier includes that feature (e.g., larger insider transaction history or pagination).
• If the remote service experiences outages, you can still query via the remote URL once service resumes; the integration relies on the remote endpoint being reachable.
• For debugging, test the endpoint with a simple request to the MCP URL (e.g., using curl) to confirm authentication and routing before integrating with Claude or other clients.