Signal8
REMOTE · MCP.SIGNAL8.AI · 2 COMPONENTS · SCANNED SEP 20
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 22189 tokens (~217/item across 102 items; 101 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 101 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 103 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Signal8 MCP server?
Signal8 is a hosted endpoint at https://mcp.signal8.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.signal8.ai
claude mcp add --transport http ai-signal8-mcp 'https://mcp.signal8.ai/mcp'
{
"mcpServers": {
"ai-signal8-mcp": {
"url": "https://mcp.signal8.ai/mcp"
}
}
} {
"servers": {
"ai-signal8-mcp": {
"type": "http",
"url": "https://mcp.signal8.ai/mcp"
}
}
} [mcp_servers.ai-signal8-mcp] url = "https://mcp.signal8.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-signal8-mcp": {
"type": "remote",
"url": "https://mcp.signal8.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-signal8-mcp --url 'https://mcp.signal8.ai/mcp' --transport streamable-http
mcp_servers:
ai-signal8-mcp:
url: "https://mcp.signal8.ai/mcp" {
"McpServers": {
"ai-signal8-mcp": {
"Transport": "http",
"Url": "https://mcp.signal8.ai/mcp"
}
}
} assistant mcp add ai-signal8-mcp -t streamable-http -u 'https://mcp.signal8.ai/mcp'
{
"mcpServers": {
"ai-signal8-mcp": {
"type": "http",
"url": "https://mcp.signal8.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 0
- Tool “get_split_history” rewrote its description, which is the text the model reads security
- Tool “get_rvol_history” rewrote its description, which is the text the model reads security
- Tool “get_premarket_scanner” rewrote its description, which is the text the model reads security
- Tool “get_premarket_scan_history” rewrote its description, which is the text the model reads security
- Schema quality: 182 → 217 ▼ functional
- New tool “get_baby_shelf_capacity” functional
- New tool “get_dilution_coverage” functional
- New tool “get_dilution_history” functional
- New tool “get_dilution_instruments” functional
- New tool “get_dilution_performance” functional
- New tool “get_dilution_risk” functional
- New tool “get_dilution_snapshot” functional
- New tool “get_recent_uplistings” functional
- New tool “get_upcoming_reverse_splits” functional
- “get_premarket_scan_history” added an optional parameter “includeUnscreened” cosmetic
- “get_rvol_history” reworded the description of “asOfTime” cosmetic
- “get_rvol_history” reworded the description of “baselineDays” cosmetic
- “screen_sec_filings” reworded the description of “sortBy” cosmetic
- “screen_sec_filings” reworded the description of “sortOrder” cosmetic
- “get_premarket_scan_history” reworded the description of “minRvol” cosmetic
- “get_premarket_scan_history” reworded the description of “baselineDays” cosmetic
- “get_premarket_scan_history” reworded the description of “asOfTime” cosmetic
- 5 Sept 26 0
- Tool “get_float” rewrote its description, which is the text the model reads security
- 2 Sept 26 0
- Tool “get_float” rewrote its description, which is the text the model reads security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 90
- Tool “get_cash_position” rewrote its description, which is the text the model reads security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.signal8.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=signal8.ai | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f2b05862b6f750b80ed22939ed20ce0f |
| SANs: signal8.ai, *.signal8.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.signal8.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| signal8.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.signal8.ai/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://mcp.signal8.ai/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://mcp.signal8.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.signal8.ai/mcp |
| Authorisation server | https://api.signal8.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.signal8.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.signal8.ai/mcp | HTTPS enforced | 308 | https://mcp.signal8.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search_sec_filings Search SEC Filings ~209
Search and list SEC filings with filtering by company (CIK), form type, and date range. Returns paginated results with filing metadata including form type, filing date, company name, and accession number. Use this to find filings before reading their content with get_filing_document or get_filing_exhibits.
| Name | Type | Req | Description |
|---|---|---|---|
| ciks | string | – | Comma-separated CIK numbers to filter by (e.g., "0000320193,0001018724") |
| dateFrom | string | – | Start date filter (YYYY-MM-DD) |
| dateTo | string | – | End date filter (YYYY-MM-DD) |
| formTypes | string | – | Comma-separated form types (e.g., "10-K,10-Q,8-K,S-1,S-3,424B5") |
| page | number | – | Page number (1-indexed, default: 1) |
| pageSize | number | – | Results per page (default: 25, max: 100) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
What is the Signal8 MCP server?
Signal8 is an MCP server listed in the public MCP registry as ai.signal8/mcp. SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents. This page covers its hosted endpoint (https://mcp.signal8.ai/mcp).
Is the Signal8 MCP server safe to use?
Signal8 scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Signal8 MCP server expose?
Signal8 exposes 101 tools: search_companies, get_company_profile, get_quote, get_market_metrics, get_short_interest, and 96 more. Their descriptions and schemas cost roughly 21,921 tokens of context every time the server is loaded.
Does the Signal8 MCP server require authentication?
Yes. Signal8 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Signal8 MCP server still maintained?
Signal8 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.