MCP servers › io.github.FinzData › finzdata-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.FinzData/finzdata-mcp

US stocks incl. delisted, futures, CPI/macro vintages, point-in-time GEX, 13F, COT, backtests. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedversion 1.0.0streamable HTTP34 tools

Summary

io.github.FinzData/finzdata-mcp is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 34 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: link does not open publicly
Tools: 34
Described as changing data: 9 of 34 toolsAI-classified
Topic: finance-and-paymentsAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (retire_strategy). That is our reading of the names; we did not call it. Source: our connection, 2026-10-23.

Worth knowing before you connect it

9 tools are described as changing something (run_backtest, publish_strategy, fork_strategy, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.
The linked repository does not open publicly, so the code cannot be reviewed through it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.0.0, published 2026-10-19 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-12 (earliest version still in the registry; older removed versions would be earlier)

Version history

5 versions listed, 2026-10-12 to 2026-10-19; 5 in the 90 days before the 2026-10-23 snapshot.

Most recent 5 versions

1.0.0 · 2026-10-19
0.2.2 · 2026-10-17
0.2.1 · 2026-10-15
0.2.0 · 2026-10-13
0.1.0 · 2026-10-12

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-19).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

34tools

0resources

0prompts

9 of 34 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

search_datasetson 36 other serversreads or searches
“Full-text search over the dataset catalog.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- querystringrequired“Search text.”
describe_dataseton 20 other serversreads or searches
“Returns the schema, coverage and field definitions of one dataset.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- datasetstringrequired“Dataset id.”
get_universeon 3 other serversreads or searches
“Returns every US symbol that was trading on as_of, including companies that later delisted (survivorship-free).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
- indexstring“Optional liquidity-ranked subset.”
- offsetinteger“Paging offset (default 0).”
- prefixstring“Only symbols starting with this.”
get_barson 2 other serversreads or searches
“Returns daily OHLCV bars for symbols between start and end, clipped to as_of (default today) so no future data leaks.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 2 required
- symbolsarrayrequired
- startstringrequired
- endstring
- barstring“Bar size: '1d' (default), or intraday '1m', '5m', '15m', '30m', '1h' (paid bundles).”
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
backtest_exportreads or searches
“Daily OHLCV bars for one symbol packaged as ready-to-load files for an open-source backtester or trading framework: backtrader, backtesting_py, vectorbt, zipline (csvdir bundle), lean (QuantConnect L…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
- symbolstringrequired
- frameworkstring
- startstring
- endstring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_fundamentals_pitreads or searches
“Returns fundamentals for one symbol as known on as_of (no restatements from the future).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- symbolstringrequired
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_macro_vintagereads or searches
“Returns a macro series as it was actually published by as_of (vintage data, no revisions from the future).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- seriesstringrequired
- startstring“Optional start date.”
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_quant_modelreads or searches
“The FinzData Quantitative Model as known on as_of: macro regime labels (financial conditions direction, financial risk direction, growth level and direction, inflation direction, macro quadrant GOLDI…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_cotreads or searches
“Returns CFTC Commitments of Traders rows for a market between start and end, clipped to as_of.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 2 required
- marketstringrequired
- startstringrequired
- endstring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_gexon 1 other serverreads or searches
“Point-in-time dealer gamma exposure for US stocks and ETFs, one row per ticker per session, each stamped with knowledge_time (17:00 New York on the session date).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
- tickerstring
- datestring“YYYY-MM-DD, cross-section mode”
- startstring
- endstring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_political_spendingreads or searches
“US election money, cleaned and rolled up (FEC + state and city filings; 2026 cycle plus 2022 and 2018).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
- tablestringrequired
- cycleinteger“Election cycle, e.g.”
- statestring“2-letter state code filter.”
- officestring
get_13freads or searches
“Returns 13F holdings matching a query as known on as_of (default today); filings after as_of are hidden.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- querystringrequired
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”

Show 22 more tools

get_eventson 38 other serversreads or searches
“Returns events of one kind between start and end (YYYY-MM-DD), clipped to as_of.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 2 required
- kindstringrequired
- all_releasesboolean“kind=macro only: true returns every data release (hundreds a week); default returns market-moving releases (CPI, payrolls, GDP, PCE, retail sales, claims, ISM …”
- startstringrequired
- endstring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
run_backteston 9 other serversruns code or commandsdescribed as changing data
“Runs a deterministic backtest from a JSON spec (universe, start, end, signal, rebalance, top_n, costs_bps, side='long'|'long_short', blind=true to hide tickers).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- specobjectrequired“Backtest spec.”
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
compare_runson 5 other serversreads or searches
“Returns a table (run_id, cagr, sharpe, max_drawdown, turnover, final_equity) for previously run backtests in this session.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- run_idsarrayrequired
publish_strategyon 2 other serversdescribed as changing data
“Runs a backtest spec (same format as run_backtest) on the server and publishes it to the FinzData Hub as a public, reproducible strategy page at data.finzdata.com/s/<slug>, forward-tracked daily from…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
5 inputs, 2 required
- specobjectrequired“Backtest spec (see run_backtest).”
- titlestringrequired“1-120 characters.”
- descriptionstring“Hypothesis: why it should work and what would falsify it.”
- visibilitystring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
fork_strategydescribed as changing data
“Copies a published Hub strategy, applies `changes` (nested fields merged, e.g.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 2 required
- slugstringrequired
- changesobjectrequired
- titlestring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
list_strategieson 19 other serversreads or searches
“Lists public FinzData Hub strategies.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- sortstring
- familystring
- limitinteger
get_strategyon 13 other serversreads or searches
“Returns one public Hub strategy: spec, server-computed backtest result, forward-tracking record and fork lineage.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- slugstringrequired
star_strategycreates or changes datadescribed as changing data
“Stars (or with unstar=true removes your star from) a public Hub strategy.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- slugstringrequired
- unstarboolean
comment_strategysends messagesdescribed as changing data
“Posts a public comment (1-2000 characters) on a Hub strategy, e.g.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- slugstringrequired
- bodystringrequired
survivorship_auditruns code or commands
“Runs your backtest spec twice: once on the point-in-time universe (delisted companies included while they traded, the honest result) and once on only the names still trading today (what a backtest on…”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- specobjectrequired“Backtest spec, same as run_backtest.”
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_futuresreads or searches
“Daily OHLCV and open interest for 139 futures markets (CME, CBOT, NYMEX, COMEX, ICE, Eurex, Cboe): every individual contract since 2007 plus continuous back-adjusted series.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 1 required
- rootstringrequired“Futures root, e.g.”
- contractstring“Optional single contract, e.g.”
- continuousboolean“Back-adjusted continuous series (default true when no contract).”
- startstring
- endstring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
get_cryptoon 1 other serverreads or searches
“OHLCV bars for crypto pairs since 2015 (BTC-USD, ETH-USD, SOL-USD and more).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
- symbolstringrequired“Pair, e.g.”
- intervalstring
- startstring
- endstring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
translate_stockcharts_scancalculates or converts
“Translates a StockCharts.com scan (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- scanstringrequired“StockCharts scan text.”
- startstring“Backtest start for the returned spec (default 2015-01-01).”
backtest_stockcharts_scanruns code or commandsdescribed as changing data
“Backtests a StockCharts.com scan on point-in-time US stocks since 2000, delisted names included: each rebalance (weekly by default) holds the stocks that pass the scan, equally weighted up to top_n, …”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
7 inputs, 2 required
- scanstringrequired“StockCharts scan text.”
- startstringrequired
- endstring
- symbolsarray“Optional universe, e.g.”
- top_ninteger“Max names held (default 50).”
- rebalancestring
- as_ofstring“Point-in-time cutoff (YYYY-MM-DD).”
register_strategydescribed as changing data
“Register a new strategy signal.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 6 required
- agent_namestringrequired
- signalstringrequired
- universestringrequired
- rebalancestringrequired
- sidestringrequired
- top_fracnumberrequired
get_verified_recordreads or searches
“Retrieve a verified strategy record by its ID.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- record_idstringrequired
verified_boardreads or searches
“Get the leaderboard of verified strategies.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- limitinteger
verify_chainon 11 other serversreads or searches
“Anyone can check no record was edited or back-dated.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
retire_strategydeletesdescribed as changing data
“Retire one of your verified strategy records: it stops accruing new forward results, keeps its full history and stays public on the Verified board marked retired.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
1 input, 1 required
- record_idstringrequired
search_mcp_serverson 14 other serversreads or searches
“finds financial MCP servers graded nightly by FinzData for health, protocol conformance and prompt-injection risk; results include install URLs.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- qstring
- categorystring
- min_gradestring
- limitinteger
get_mcp_serveron 7 other serversreads or searches
“retrieves a financial MCP server listing with tools, probe history, issues and verified-data status.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- slugstringrequired
claim_mcp_serveron 2 other serversdescribed as changing data
“claims a listing for the calling API key so its owner can enable price-accuracy checks; first claimant wins; contact info@finzdata.com to dispute.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
- slugstringrequired

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 34 tools
Says what it returns: 82% of 34 tools
States limits, defaults or errors: 29% of 21 tools
Says when to use it: 0% of 34 tools
Items covered per tool: 2.4 of 4 on average

Counted from the listing

Parameters with a description: 42% of 99
Tools with a description: 100% of 34
Typical description length: 267 characters

The tool set

Counted from the listing

Tools: 34
Size of the list: about 6,459 tokens for an agent to load (characters ÷ 4)
Naming: 34 of 34 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 34 of 34 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://api.finzdata.com/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

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

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.finzdata.com/mcp --transport http

Optional settings the entry also lists (left out above): X-API-Key.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint api.finzdata.com/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23
Repository github.com/finzdata/finzdata-mcp	Does not open (not found or private)	differs	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.FinzData

Repository: github.com/finzdata/finzdata-mcp — does not open publicly

Source: the registry entry and api.github.com · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe linked repository returned HTTP 404: it does not exist or is private.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.FinzData/finzdata-mcp

Answered from the data above

Is io.github.FinzData/finzdata-mcp safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: The repository it links to does not open publicly, so its code cannot be inspected through that link. 9 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.FinzData/finzdata-mcp need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.FinzData/finzdata-mcp been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.github.FinzData/finzdata-mcp do?

It lists 34 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages, run code or commands and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.FinzData/finzdata-mcp change or delete data?

9 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Where is the source code of io.github.FinzData/finzdata-mcp?

The registry links to github.com/finzdata/finzdata-mcp, but that link does not open publicly, so the code cannot be inspected through it.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.WellApp-ai/well-mcpWellalso has tools that calculates or converts, creates or changes data, deletes, runs code or commands, reads or searches, sends messagescompare with this one
io.github.spfunctions/simplefunctionsalso has tools that calculates or converts, creates or changes data, deletes, runs code or commands, reads or searches, sends messagescompare with this one
io.github.longsizhuo/openinvestopenInvestalso has tools that calculates or converts, creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
io.github.lightningfaucet/lightning-wallet-mcpLightning Walletalso has tools that calculates or converts, creates or changes data, deletes, reads or searches, sends messagescompare with this one
io.github.lightningfaucet/mcp-serveralso has tools that calculates or converts, creates or changes data, deletes, reads or searches, sends messagescompare with this one
io.github.MangroveTechnologies/mangroveaiMangroveAIalso has tools that calculates or converts, creates or changes data, deletes, runs code or commands, reads or searchescompare with this one

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,326 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 34 tools, 0 resources, 0 prompts.
3,864 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

finance-and-payments

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

does not apply

no existing GitHub repository

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

not stated

repository link is dead (HTTP 404), so activity cannot be read

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.FinzData/finzdata-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.FinzData/finzdata-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.FinzData/finzdata-mcp)](https://protocolprobe.com/mcp/servers/io.github.FinzData/finzdata-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology