Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FinzData Workspace

REMOTE · WORKSPACE.FINZDATA.COM

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

+3 this week 71 Trust /100

Last scanned (13 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security71
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 683 tokens (~85/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 12% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 11 Nov 26 +34
    • Authorization: pass → fail ▼ security
    • Transport: unverified → pass ▲ security
    • 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 security
    • Endpoint reachability: behind authorisation → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.10 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Server version: 1.3.5 → 1.3.2 functional
  • 10 Nov 26 −34
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Authorization: fail → pass ▲ security
    • First check of Authorization: pass security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 9 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 21 Nov 2026 · Probed https://workspace.finzdata.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=finzdata.com CN=WE1,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 d5c7690822445bb40e172af03de857d1
SANs: finzdata.com, workspace.finzdata.com, *.workspace.finzdata.com
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 workspace.finzdata.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
finzdata.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://workspace.finzdata.com/mcp Verified 200
http (plaintext) http://workspace.finzdata.com/mcp Inconclusive 405
MCP tools · 8 exposed · ~603 tokens

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 →

Tool Tokens
finzdata_get ~116

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.

NameTypeReqDescription
paramsobject––
pathstringyes–
save_tostring––

No output schema declared.

No examples provided.

strategy_list ~84

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.

NameTypeReqDescription
familystring––
limitnumber––
sortstring––

No output schema declared.

No examples provided.

strategy_run ~117

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.

NameTypeReqDescription
endstring––
saveboolean–Default true.
slugstringyes–

No output schema declared.

No examples provided.

workspace_delete ~47

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

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

workspace_list ~40

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

NameTypeReqDescription
pathstring––

No output schema declared.

No examples provided.

workspace_read ~37

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

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

workspace_run ~108

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.

NameTypeReqDescription
codestringyes–
inputobject–JSON value passed to your default export.
timeout_msnumber––

No output schema declared.

No examples provided.

workspace_write ~54

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

NameTypeReqDescription
contentstringyes–
pathstringyes–

No output schema declared.

No examples provided.

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.

remote · workspace.finzdata.com

# add to Claude Code
claude mcp add --transport http com-finzdata-workspace 'https://workspace.finzdata.com/mcp'
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.