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.

Datavidence Financials

PYPI · DATAVIDENCE-FINANCIALS

Normalized US-GAAP financial statements & fundamentals from SEC EDGAR, as MCP tools for LLM agents.

−15 this week 64 Trust /100

Last scanned (13 hours ago)

Scores higher than 61% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security32
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects mcp 2.1.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 42 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1419 tokens (~236/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • 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 package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 0
    • Provenance: unverified → fail ▼ security
  • 1 Nov 26 +15
    • Provenance: fail → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 30 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
  • 22 Oct 26 +1
    • Provenance: unverified → fail ▼ security
    • Security disclosure: unverified → pass ▲ functional
  • 21 Oct 26 −1
    • Provenance: fail → unverified ▼ security
    • Security disclosure: pass → unverified ▼ 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 5 Nov 2026 · Analysed pypi/datavidence-financials@0.1.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 4 findings
ID CVE Severity Vector Fix available
GHSA-5h93-6whr-6q8j CVE-2026-116685 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-84m7-p3x7-pcfv CVE-2026-59951 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rwrf-2pqf-9j8j CVE-2026-116686 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-w4fh-qvv9-3v23 CVE-2026-116684 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 31 packages
Packages resolved 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,368 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
get_financials ~298

Retrieve normalized US-GAAP financial statements (income statement, balance sheet, cash flow) for one company and fiscal year, from SEC EDGAR XBRL. Identify the company by `ticker` OR `cik`. Use `as_of` (ISO YYYY-MM-DD) to get the figures as originally reported on that date — no look-ahead bias — for backtests. Set `include_provenance=true` to attach, for every value, the SEC accession, filed date, and a direct EDGAR source URL for citation. Set `include_ratios=true` for margins, ROA/ROE, and leverage derived from the same statements. Returns the normalized data object.

NameTypeReqDescription
as_of––ISO date YYYY-MM-DD. Return figures as originally reported on that date (no look-ahead). Omit for the latest reported figures.
cik––SEC Central Index Key, e.g. "0000320193". Give this or `ticker`.
include_provenanceboolean–Attach the SEC accession, filed date and EDGAR URL behind every value.
include_ratiosboolean–Add margins, ROA/ROE and leverage computed from the same statements.
ticker––Stock ticker, e.g. "AAPL". Give this or `cik`.
yearintegeryesFiscal year, e.g. 2023.

No output schema declared.

No examples provided.

get_financials_batch ~334

Retrieve normalized US-GAAP financials for MANY companies in one call — use this to compare peers or scan a set for a single fiscal year. Pass companies as comma-separated `tickers` (e.g. "AAPL,MSFT,GOOGL") and/or `ciks`; up to 25 symbols total, all for the same `year`. `as_of`, `include_provenance`, and `include_ratios` behave as in get_financials and apply to every symbol. Each company returns its own result — either `data` or an `error` with a recovery hint — so one bad symbol never fails the batch. The whole call counts as a SINGLE request against your monthly quota, so prefer it over many get_financials calls when you need several companies.

NameTypeReqDescription
as_of––ISO date YYYY-MM-DD. Return figures as originally reported on that date (no look-ahead). Omit for the latest reported figures.
ciks––Comma-separated SEC CIKs (25 symbols max, with `tickers`).
include_provenanceboolean–Attach the SEC accession, filed date and EDGAR URL behind every value.
include_ratiosboolean–Add margins, ROA/ROE and leverage computed from the same statements.
tickers––Comma-separated tickers, e.g. "AAPL,MSFT,GOOGL" (25 symbols max, with `ciks`).
yearintegeryesFiscal year, e.g. 2023.

No output schema declared.

No examples provided.

get_revisions ~318

Show how a company's reported figures for a fiscal year CHANGED across filings — as originally reported, then each restatement. A company re-reports every fiscal year as a comparative in later filings, and when a number changes, that is a restatement. This returns the full series for each metric: every reported value with the date it was filed, the form (10-K/10-Q), the SEC accession and a direct EDGAR link, plus whether it was restated and by how much. Use it to answer "has this been restated?", to show a figure's history, or to explain why a backtest on today's data would not match what an investor could have known at the time. Identify the company by `ticker` OR `cik`; narrow with `metrics` (comma-separated, e.g. "total_revenue,net_income") or omit for all. get_financials returns the LATEST reported figure; its `as_of` parameter returns the value as known on a date; this shows the whole series at once.

NameTypeReqDescription
cik––SEC Central Index Key, e.g. "0000320193". Give this or `ticker`.
metrics––Comma-separated metric names, e.g. "total_revenue,net_income". Omit for all.
ticker––Stock ticker, e.g. "AAPL". Give this or `cik`.
yearintegeryesFiscal year, e.g. 2023.

No output schema declared.

No examples provided.

get_usage ~71

Report the calling API key's current monthly quota: tier, monthly limit, requests used and remaining this billing month, and when it resets. Free to call — it does NOT consume quota. Check it before a large batch or a long run so you can pace requests and avoid a hard rate-limit (429).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_filings ~198

List a company's recent SEC filings (newest first) from the EDGAR submissions index — a lean company header plus filing rows. Identify the company by `ticker` OR `cik`. Optionally filter by `form` (e.g. "10-K", prefix-matched so it includes amendments like "10-K/A") and cap the number of rows with `limit` (1-100). Use this to discover which fiscal years or filings are available before calling get_financials.

NameTypeReqDescription
cik––SEC Central Index Key, e.g. "0000320193". Give this or `ticker`.
form––Form type filter, prefix-matched, e.g. "10-K" (includes 10-K/A).
limitinteger–Maximum rows to return (1-100).
ticker––Stock ticker, e.g. "AAPL". Give this or `cik`.

No output schema declared.

No examples provided.

search_companies ~149

Find a company's ticker and CIK by ticker or company name. Use this FIRST whenever you have a company name but not its ticker or CIK — every other tool needs one of those. Searches SEC's master list: "berkshire" returns BRK-B with its CIK, "mobil" returns XOM. Ranked so the obvious answer wins (an exact ticker beats a company whose name merely contains the text). `limit` caps the number of matches (1-25).

NameTypeReqDescription
limitinteger–Maximum matches to return (1-25).
querystringyesCompany name or ticker, e.g. "berkshire" or "XOM".

No output schema declared.

No examples provided.

Install

How do I install the Datavidence Financials MCP server?

Datavidence Financials runs locally as a PyPI package, launched with uvx datavidence-financials. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · datavidence-financials

# add to Claude Code
claude mcp add ai-datavidence-datavidence-financials -- uvx datavidence-financials
Common questions

What is the Datavidence Financials MCP server?

Datavidence Financials is an MCP server listed in the public MCP registry as ai.datavidence/datavidence-financials. Normalized US-GAAP financial statements & fundamentals from SEC EDGAR, as MCP tools for LLM agents. This page covers its PyPI package (datavidence-financials).

Is the Datavidence Financials MCP server safe to use?

Datavidence Financials scores 64 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 5 November 2026. 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 Datavidence Financials MCP server expose?

Datavidence Financials exposes 6 tools: get_financials, list_filings, get_financials_batch, get_revisions, search_companies, get_usage. Their descriptions and schemas cost roughly 1,368 tokens of context every time the server is loaded.

Is the Datavidence Financials MCP server still maintained?

Datavidence Financials 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.

What licence is the Datavidence Financials MCP server under?

Datavidence Financials declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Datavidence Financials MCP server?

VerifyMCP ran 15 checks on Datavidence Financials, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Datavidence Financials: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.