Home / MCP registry index / com.finzdata/mcp

FinzData

com.finzdata/mcp in the official MCP registry. Endpoint https://api.finzdata.com/mcp.

The registry describes it as: Point-in-time stocks, ETFs, futures, GEX, crypto, FX, macro, COT, 13F, ships, ports, flights, power.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http finzdata https://api.finzdata.com/mcp

{
  "mcpServers": {
    "finzdata": {
      "url": "https://api.finzdata.com/mcp"
    }
  }
}

code --add-mcp '{"name":"finzdata","type":"http","url":"https://api.finzdata.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_datasets describe_dataset get_universe get_bars backtest_export get_fundamentals_pit get_macro_vintage get_quant_model get_cot get_gex get_political_spending get_13f get_events run_backtest run_strategy compare_runs publish_strategy fork_strategy list_strategies get_strategy star_strategy comment_strategy survivorship_audit get_futures get_futures_rolls get_crypto get_fx get_index get_ticks get_global_pulse translate_stockcharts_scan backtest_stockcharts_scan register_strategy get_verified_record verified_board verify_chain retire_strategy search_mcp_servers get_mcp_server claim_mcp_server

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-08): 6267606901e0b3c6. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-finzdata-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-finzdata-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers · Finance and markets MCP servers · Travel MCP servers