# SignalDock (remote · www.signaldock.app)

Market reports, earnings history, research, portfolio analysis and read-only Workspace tools.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.signaldock.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/homeaccount7-signaldock/api-mcp.md), [page](https://verifymcp.io/servers/homeaccount7-signaldock/api-mcp)

## Channel facts

- Endpoint: `https://www.signaldock.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1333 tokens (~111/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 22% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SignalDock MCP server?

SignalDock is a hosted endpoint at https://www.signaldock.app/api/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.

### Claude

```bash
claude mcp add --transport http homeaccount7-signaldock 'https://www.signaldock.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "homeaccount7-signaldock": {
      "url": "https://www.signaldock.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "homeaccount7-signaldock": {
      "type": "http",
      "url": "https://www.signaldock.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.homeaccount7-signaldock]
url = "https://www.signaldock.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "homeaccount7-signaldock": {
      "type": "remote",
      "url": "https://www.signaldock.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add homeaccount7-signaldock --url 'https://www.signaldock.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  homeaccount7-signaldock:
    url: "https://www.signaldock.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "homeaccount7-signaldock": {
      "Transport": "http",
      "Url": "https://www.signaldock.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add homeaccount7-signaldock -t streamable-http -u 'https://www.signaldock.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "homeaccount7-signaldock": {
      "type": "http",
      "url": "https://www.signaldock.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 69)

First indexed and scored.

## MCP tools (12)

### `read_report` (~130 tokens)

Read a SignalDock report

Read one of fifteen published market reports without signing in. Large responses return a field directory; select a path and page arrays. Never generates or emails a report.

Input parameters:

- `before` (string): Predictor edition list: next cursor from the previous page.
- `editions` (boolean): Predictor only: list published editions.
- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `report` (string, required)
- `week` (string): Predictor only: Monday edition date; defaults to latest.

### `earnings_history` (~141 tokens)

Research earnings history

Retained earnings events and sector × market-cap comparisons with provenance and coverage. For page > 1 reuse the snapshot returned on page 1. Comparisons are descriptive, not predictions.

Input parameters:

- `date_from` (string)
- `date_to` (string)
- `limit` (integer)
- `offset` (integer)
- `page` (integer)
- `page_size` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `season` (string)
- `snapshot` (string)
- `symbol` (string)
- `target_symbol` (string)

### `options_question` (~126 tokens)

Answer a focused options question

Requires a SignalDock account connection. Expected move, near-money skew/activity or IV history for one equity or futures root. At most five provider operations. Skew/activity require expiration. Coverage is bounded, never whole-chain totals.

Input parameters:

- `expiration` (string)
- `history_days` (integer)
- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `question` (string, required)
- `strike_count` (integer)
- `symbol` (string, required)

### `research_company` (~99 tokens)

Research a security

Requires a SignalDock account connection. Technical analysis, forecast, analyst estimates, earnings context, valuation or capital structure. Returns existing API coverage and missing-data warnings. A pending response is not a completed analysis.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `section` (string, required)
- `symbol` (string, required)

### `compare_symbols` (~80 tokens)

Compare two securities

Requires a SignalDock account connection. Read correlation, relative action and divergence analytics for two distinct securities.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `symbol1` (string, required)
- `symbol2` (string, required)

### `trading_day` (~87 tokens)

Read a simulated trading day

Read the public Trading Agent day feed or list available days. Public history starts November 1, 2026. Updates and fills are a narrative simulation; no orders are placed.

Input parameters:

- `date` (string)
- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.

### `read_archive` (~74 tokens)

Read report archives

List retained daily archive dates, or read a saved daily snapshot. Requires account research access. Does not regenerate reports.

Input parameters:

- `date` (string)
- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.

### `read_options_history` (~71 tokens)

Read retained options history

Read a retained options-history snapshot using the identifier returned by options_question. Requires account research access.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `snapshot` (string, required)

### `read_workspace` (~93 tokens)

Read your Workspace

Read your saved Rules, Notes and Trades from Playbook, or your saved Security Snapshot. Requires explicit Workspace consent. Trades are your written strategies, not brokerage executions. Never edits content or generates/emails reports.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `section` (string)

### `read_account_context` (~77 tokens)

Read your account context

Read your configured watchlists, symbols, service access and saved broker portfolio summary. Requires both Workspace and portfolio consent. Returns only the connected account owner’s data.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.

### `read_portfolio` (~130 tokens)

Read your saved portfolios

List your saved and connected broker portfolios, read holdings, balances, saved metrics/account performance, or retained analysis history. Requires portfolio consent. Uses saved dated snapshots; never synchronizes brokers, imports records, places orders or generates a narrative. Follow nextCursor for list/history pages.

Input parameters:

- `action` (string)
- `analysis_id` (string)
- `cursor` (string)
- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.
- `source_id` (string)

### `analyze_portfolio` (~126 tokens)

Analyze supplied portfolio holdings

Run the existing Portfolio API for up to 50 supplied stock holdings with shares and optional per-share cost basis. Requires portfolio consent and existing service access/API allowance. Does not save a portfolio, place orders or synchronize a broker. Saved option holdings can be read with read_portfolio; this API accepts the existing stock-holdings contract.

Input parameters:

- `benchmark` (string)
- `holdings` (array, required)
- `limit` (integer)
- `offset` (integer)
- `path` (array): Object keys or array indices from the returned field directory. Empty selects the root.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/homeaccount7-signaldock/api-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69

## Common questions

### What is the SignalDock MCP server?

SignalDock is an MCP server listed in the public MCP registry as io.github.homeaccount7/signaldock. Market reports, earnings history, research, portfolio analysis and read-only Workspace tools. This page covers its hosted endpoint (https://www.signaldock.app/api/mcp).

### Is the SignalDock MCP server safe to use?

SignalDock scores 70 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 SignalDock MCP server expose?

SignalDock exposes 12 tools: read_report, earnings_history, options_question, research_company, compare_symbols, and 7 more. Their descriptions and schemas cost roughly 1,234 tokens of context every time the server is loaded.

### Does the SignalDock MCP server require authentication?

No. We connected to SignalDock without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SignalDock MCP server still maintained?

SignalDock is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.signaldock.app/api/mcp
- Website: https://www.signaldock.app/integrations
- Changelog RSS feed: https://verifymcp.io/servers/homeaccount7-signaldock/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/homeaccount7-signaldock/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/homeaccount7-signaldock/api-mcp