Connect your AI
to 33,000+ multi-market filings

MCP (Model Context Protocol) is the open standard Anthropic published in 2024 to connect AI agents to external data sources. Think USB-C: your AI plugs into the server once and reaches everything it exposes, with no glue code.

On Insiders Trades, the MCP server turns our 14 REST endpoints into 29 richly documented tools (with JSON Schema definitions), optimised for consumption by an LLM:

• Plain-language descriptions that spell out exactly when to call each tool.
• Strict input schemas (type plus min/max constraints) so the model never passes invalid parameters.
• Composite tools that combine several endpoints in one call (e.g. get_company_full_profile returns identity plus latest trades plus backtest stats in a single shot).
• Temporal metadata on every response (latencyMs, generatedAt) so the agent can reason about freshness.

The server runs at POST https://insiders-trades.com/api/mcp. Plain HTTP transport (no stdio), JSON-RPC 2.0 envelope, open CORS (Access-Control-Allow-Origin: *).

┌─────────────────┐ 1. initialize ┌────────────────────┐
│ │ ────────────────────▶ │ │
│ AI client │ 2. tools/list │ MCP server │
│ (Claude, │ ────────────────────▶ │ POST /api/mcp │
│ Cursor, │ 3. tools/call │ JSON-RPC 2.0 │
│ Windsurf…) │ ────────────────────▶ │ │
│ │ +arguments │ executeTool() │
└────────▲────────┘ │ routing + auth │
 │ │ │ │
 │ │ ▼ │
 │ content[0].text │ Bearer <key> │
 │ (JSON stringified) │ │ │
 │ │ ▼ │
 └────────────────────────────────┤ Prisma / Postgres │
 │ (read-only) │
 └────────────────────┘

On the client side there is nothing to code: Claude Desktop / Cursor / Windsurf / VS Code (+ the Continue extension) speak JSON-RPC MCP natively. Just add the URL to their config file.

Supported methods

Example tools/call request

{
 "jsonrpc": "2.0",
 "id": 1,
 "method": "tools/call",
 "params": {
 "name": "search_top_signals",
 "arguments": {
 "direction": "BUY",
 "lookbackDays": 7,
 "minScore": 50,
 "limit": 5
 }
 }
}

Every tools/list and tools/call must include your Insiders Trades API key. Two formats are accepted in production, in order of priority:

1. Authorization: Bearer <key> · preferred, supported by modern MCP clients (Claude Desktop ≥ 3.7, Cursor, Windsurf).
2. X-Api-Key: <key> · alternative header.

{
  "mcpServers": {
    "insiders-trades": {
      "url": "https://insiders-trades.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${INSIDERS_TRADES_API_KEY}"
      }
    }
  }
}

To generate a key, head to /account/api-keys (5 seconds). The key is shown only once, so copy it right away. It shares the same quota as the REST API: Pro 334 requests per UTC day, Quant 3,334 requests per UTC day.

Grouped into 4 families by use. Each tool returns a self-contained JSON payload with latency metadata.

5 minutes, 3 steps, no code:

The URL to copy

https://insiders-trades.com/api/mcp

Per-client walkthrough

{
 "mcpServers": {
 "insiders-trades": {
 "type": "http",
 "url": "https://insiders-trades.com/api/mcp",
 "headers": {
 "Authorization": "Bearer sit_live_YOUR_KEY_HERE"
 }
 }
 }
}

Once the server is configured, ask your AI this question:

The AI should list 29 tools grouped into 4 families (Discovery, Enrichment, System, Composite). If it does not:

• Check that the MCP server is actually enabled in the client settings.
• Fully relaunch the app (not just a window reload).
• Check the API key: curl https://insiders-trades.com/api/mcp should return a welcome JSON; adding auth and calling tools/list should return the catalog.
• Inspect the AI client logs (Claude Desktop exposes them via View logs).

Example prompts that trigger tools