Signal8 MCP Server

Official

by signal8ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Cross-Company Insider Trading

get_insider_cross_company

Read-only

Search the entire universe for insiders active across multiple companies. Filter by name, transaction type, or date to identify coordinated trading patterns and market-wide trends.

Instructions

Discover insider trading patterns across multiple companies. Unlike get_insiders which shows insider activity for a single ticker, this tool searches the entire universe to find insiders active across multiple companies, cluster buying patterns, and large transactions. Filter by insider name, transaction type, or date range. Useful for detecting coordinated insider activity, cross-company insider networks, and market-wide buying/selling trends.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results to return (default: 10, max: 100)
`offset`	No	Offset for pagination (default: 0)
`endDate`	No	End date for transaction range in ISO format (e.g., "2025-12-31")
`startDate`	No	Start date for transaction range in ISO format (e.g., "2025-01-01")
`insiderName`	No	Filter by insider name (partial match, e.g., "Musk" or "Cohen")
`transactionType`	No	Filter by transaction type: "P" (purchase), "S" (sale), "A" (grant/award), "M" (conversion)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 1, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds context beyond readOnlyHint: describes searching entire universe, detecting networks and clusters. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, front-loaded with purpose and differentiation, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists and all parameters described, the description adequately explains the tool's unique value, use cases, and scope. No need to elaborate on return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% so baseline is 3. Description mentions filtering by name, type, date range which aligns with schema but does not add new meaning beyond what schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'discover' and resource 'insider trading patterns across multiple companies'. Distinctly differentiates from sibling get_insiders which focuses on a single ticker.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts with sibling get_insiders, guiding when to use this tool (cross-company) vs single-ticker. Mentions filtering options but lacks explicit 'when not to use' scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server