# FinzData Workspace (remote · workspace.finzdata.com)

AI workspace with FinzData built in: stocks, futures, options GEX, macro, crypto data and code runs.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `workspace.finzdata.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-finzdata-workspace/workspace.md), [page](https://verifymcp.io/servers/com-finzdata-workspace/workspace)

## Channel facts

- Endpoint: `https://workspace.finzdata.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.4.2`

## 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-21.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 683 tokens (~85/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 12% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the FinzData Workspace MCP server?

FinzData Workspace is a hosted endpoint at https://workspace.finzdata.com/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 com-finzdata-workspace 'https://workspace.finzdata.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-finzdata-workspace": {
      "url": "https://workspace.finzdata.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-finzdata-workspace": {
      "type": "http",
      "url": "https://workspace.finzdata.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-finzdata-workspace]
url = "https://workspace.finzdata.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-finzdata-workspace": {
      "type": "remote",
      "url": "https://workspace.finzdata.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-finzdata-workspace --url 'https://workspace.finzdata.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-finzdata-workspace:
    url: "https://workspace.finzdata.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-finzdata-workspace": {
      "Transport": "http",
      "Url": "https://workspace.finzdata.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-finzdata-workspace -t streamable-http -u 'https://workspace.finzdata.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-finzdata-workspace": {
      "type": "http",
      "url": "https://workspace.finzdata.com/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-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

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

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 66, +34)

- [security regression] Authorization: pass → fail
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] Tool “finzdata_get” rewrote its description, which is the text the model reads
- [security] Tool “strategy_list” rewrote its description, which is the text the model reads
- [security] Tool “strategy_run” rewrote its description, which is the text the model reads
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] Tool coverage: unverified → 100
- [functional] Server version: 1.3.5 → 1.3.2

### 2026-11-10 (score 32, −34)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-09 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `finzdata_get` (~116 tokens)

Get FinzData API data

Read-only GET request to the FinzData REST API (docs: https://finzdata.com/docs) with your key (for example /v1/prices/daily, /v1/futures/daily, /v1/gex/daily, /v1/cot, /v1/pulse/{name}, /v1/model/latest). Optionally save the result into your workspace with save_to.

Input parameters:

- `params` (object)
- `path` (string, required)
- `save_to` (string)

### `strategy_list` (~84 tokens)

List FinzData strategies

List public FinzData Hub strategies (momentum, trend, mean reversion, value, factor, AI Tournament). sort: robust (deflated Sharpe), forward, new, forks. Every listed strategy is free to re-run on its full history with strategy_run.

Input parameters:

- `family` (string)
- `limit` (number)
- `sort` (string)

### `strategy_run` (~117 tokens)

Re-run a FinzData strategy

Re-run a listed FinzData strategy exactly as published, on its full point-in-time history through end (default today), on the FinzData servers. Free on every plan. Saves spec.json and result.json to /workspace/strategies/<slug>/ so you can analyse them with workspace_run. Changing the strategy or testing your own idea over full history needs a FinzData purchase; the free window still applies there.

Input parameters:

- `end` (string)
- `save` (boolean): Default true.
- `slug` (string, required)

### `workspace_run` (~108 tokens)

Run code in the workspace

Run a JavaScript (ES module) program inside your workspace. It must `export default async function (input) { ... }` and return JSON. Use `import { get } from "codemode:finzdata"` for data and `import fs from "node:fs/promises"` for files under /workspace. No other network access.

Input parameters:

- `code` (string, required)
- `input` (object): JSON value passed to your default export.
- `timeout_ms` (number)

### `workspace_write` (~54 tokens)

Write a workspace file

Write a text file in your FinzData Workspace (paths live under /workspace and persist between sessions; docs: https://finzdata.com/workspace).

Input parameters:

- `content` (string, required)
- `path` (string, required)

### `workspace_read` (~37 tokens)

Read a workspace file

Read a text file from your FinzData Workspace (docs: https://finzdata.com/workspace).

Input parameters:

- `path` (string, required)

### `workspace_list` (~40 tokens)

List workspace files

List a directory in your FinzData Workspace (default /workspace; docs: https://finzdata.com/workspace).

Input parameters:

- `path` (string)

### `workspace_delete` (~47 tokens)

Delete a workspace file

Delete a file or directory in your FinzData Workspace (a per-key file store on Cloudflare; docs: https://finzdata.com/workspace).

Input parameters:

- `path` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-finzdata-workspace/workspace#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 67
- 2026-11-12: 67
- 2026-11-11: 66
- 2026-11-10: 32
- 2026-11-09: 66
- 2026-11-08: 65

## Common questions

### What is the FinzData Workspace MCP server?

FinzData Workspace is an MCP server listed in the public MCP registry as com.finzdata/workspace. AI workspace with FinzData built in: stocks, futures, options GEX, macro, crypto data and code runs. This page covers its hosted endpoint (https://workspace.finzdata.com/mcp).

### Is the FinzData Workspace MCP server safe to use?

FinzData Workspace scores 71 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 FinzData Workspace MCP server expose?

FinzData Workspace exposes 8 tools: finzdata_get, strategy_list, strategy_run, workspace_run, workspace_write, and 3 more. Their descriptions and schemas cost roughly 603 tokens of context every time the server is loaded.

### Does the FinzData Workspace MCP server require authentication?

Yes. FinzData Workspace 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 FinzData Workspace MCP server still maintained?

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

### What did VerifyMCP test on the FinzData Workspace MCP server?

VerifyMCP ran 12 checks on FinzData Workspace, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FinzData Workspace: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://workspace.finzdata.com/mcp
- Website: https://finzdata.com/workspace
- Changelog RSS feed: https://verifymcp.io/servers/com-finzdata-workspace/workspace.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-finzdata-workspace/workspace/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-finzdata-workspace/workspace.json
- HTML version of this page: https://verifymcp.io/servers/com-finzdata-workspace/workspace
