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.

Company fundamentals by filing date

REMOTE · WWW.TRADINGAGENTAPP.COM · 2 COMPONENTS

Company financials from official filings, each figure keyed to its filing date.

−48 this week 25 Trust /100

Last scanned (13 hours ago)

Scores higher than 10% 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 Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

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.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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.

  • 21 Nov 26 −51
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.40 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 19 Nov 26 +1
    • Tool “get_group_structure” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1746 → 2679 ▼ functional
    • Server version: 1.2.0 → 1.3.0 functional
    • New tool “get_company_status” functional
    • New tool “get_group_structure” functional
    • New tool “compare_companies” functional
  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 10 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_data_dictionary” rewrote its description, which is the text the model reads security
    • Schema quality: good → excellent functional
    • Server version: 1.1.0 → 1.2.0 functional
  • 9 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_fundamentals_history” rewrote its description, which is the text the model reads security
    • Tool “get_coverage” rewrote its description, which is the text the model reads security
    • Tool “search_companies” rewrote its description, which is the text the model reads security
    • Tool “get_latest_fundamentals” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: excellent → good functional
    • Server version: 1.0.0 → 1.1.0 functional
    • “get_fundamentals_history” added an optional parameter “compact” cosmetic
    • “get_coverage” added an optional parameter “compact” cosmetic
    • “get_fundamentals_history” added an optional parameter “max_rows” cosmetic
    • “get_latest_fundamentals” added an optional parameter “compact” cosmetic
    • “search_companies” reworded the description of “market” cosmetic
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://www.tradingagentapp.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.tradingagentapp.com CN=YR2,O=Let's Encrypt,C=US 29 Sept 2026 28 Dec 2026 RSA 2048 SHA256-RSA 546f5578d359e41d2e6d5a6b44cc97e592f
SANs: www.tradingagentapp.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.tradingagentapp.com. — Not signed

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

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.tradingagentapp.com/api/mcp HTTP error 503
http (plaintext) http://www.tradingagentapp.com/api/mcp HTTPS enforced 308 https://www.tradingagentapp.com/api/mcp
MCP tools · 8 exposed · ~2,530 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
compare_companies ~455

The latest filed value of one to 5 metrics for up to 10 companies, side by side, each value with its period (fy, fp, end), filing date, basis (consolidated, solo or reported), unit and source register. Values are as filed, in each company's own currency and unit, never converted; compare fy, fp, end and basis before reading two values together. Inputs: tickers (list), metric (comma-separated, e.g. revenue,net_income), as_of (only filings dated on or before that day; needs a licence key), compact (true leaves out market_notes). Each company counts as one call against the rate limit and, for a key with a company limit, as one company read. Figures are as filed, each keyed to its filing date (`filed`) as its market records it (how each market dates a filing: https://www.tradingagentapp.com/fundamentals/methodology). .TW quarterly values are already SINGLE-QUARTER amounts, so differencing adjacent quarters gives wrong figures. For a quarterly row (US, Taiwan) fy and fp are the CALENDAR quarter containing the period end, not the company's fiscal quarter. Each reply's `market_notes` and `schema` state the per-market caveats (solo or group accounts, lawful gaps, charities, flags in `form`). Detailed line items follow local accounting rules and keep the filed sign (capex is negative in Taiwan and Japan); get_data_dictionary defines them per market. The source licences require each reply's `attribution` and `licence` notices to accompany the figures.

NameTypeReqDescription
as_ofstring–Filing-date cut-off, YYYY-MM-DD: only filings dated on or before that day
compactboolean–true leaves out the long per-market notes (market_notes, schema) to save tokens; default false
metricstringyes1-5 comma-separated metrics, e.g. revenue,net_income,assets
tickersarrayyes1-10 tickers, e.g. ["AAPL", "MSFT"] or ["0403091220.BE", "775670417.FR"]

No output schema declared.

No examples provided.

get_company_status ~230

The register's legal status of one company: value (active, no_end_recorded, in_restructuring, dissolution_recorded, in_liquidation, bankrupt, dissolved, deregistered), the register's own code and label, since (the date the source gives for it taking effect; null where it gives none), as_of (the date the source stated it) and availability (available, none_stated, not_collected, unavailable, not_in_warehouse). Status is collected for some register markets only (get_data_dictionary's company_attributes lists them); the others answer not_collected. no_end_recorded means the register records no end and no open proceeding; it is not a statement that the company is active. Inputs: ticker; as_of (the status on that day by the source's own dates; needs a licence key).

NameTypeReqDescription
as_ofstring–Status on this day, YYYY-MM-DD, by the source's own dates (needs a licence key)
tickerstringyesTicker symbol, e.g. AAPL or 2330.TW

No output schema declared.

No examples provided.

get_coverage ~114

Markets covered, company counts, history depth per market, the companies that answer with full history without a licence key (full_history_sample), the metric vocabulary, the source attributions that must travel with the data, and the licence the data is supplied under (for a time-limited key, its terms and end date). compact (true) leaves out the per-market notes and accounting descriptions.

NameTypeReqDescription
compactboolean–true leaves out the long per-market notes (market_notes, schema) to save tokens; default false

No output schema declared.

No examples provided.

get_data_dictionary ~263

The data dictionary of the detailed line items: for every metric, its definition, which filed line each market reads it from (or why a market has none), and the measured share of that market's company-periods that carry it; the figures we calculate from them, with their formulas; and the rules that apply to all of them (dating, signs, annual-only cash-flow lines, small employers). Use it before comparing a line item across markets, or to learn what a line-item code means. It also defines company.industry and company.status (the register's industry code and legal status, with source and dates), per market. Codes: trade_receivables, trade_and_other_receivables, inventories, trade_payables, trade_and_other_payables, ppe, noncurrent_assets, current_assets, current_liabilities, retained_earnings, depreciation_amortization, interest_expense, cash_flow_operating, capex, minority_interest, temporary_equity, land_and_buildings, land, buildings, pension_provisions, cost_of_materials, purchases_of_goods, purchases_of_materials, wages_and_salaries, operating_taxes, income_tax; calculated: free_cash_flow, working_capital, current_ratio, ebitda.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_fundamentals_history ~493

The stored figures for one ticker, one row per metric and period, each with its period (fy, fp), period end, filing date and form. Use it for trends and for what was on file at a past date. Inputs: ticker, metric (comma-separated), from (earliest period end), as_of (only filings dated on or before that day), max_rows (1-250, default 250), compact (true leaves out market_notes and schema). Without a licence key, a company outside the full-history sample answers with its most recent reported fiscal year only: full_history false and history_depth say so, and older filings exist. Long histories are capped at max_rows, keeping the most recent rows of EVERY metric (per_metric says how many of each); metric and from select older rows. Figures are as filed, each keyed to its filing date (`filed`) as its market records it (how each market dates a filing: https://www.tradingagentapp.com/fundamentals/methodology). .TW quarterly values are already SINGLE-QUARTER amounts, so differencing adjacent quarters gives wrong figures. For a quarterly row (US, Taiwan) fy and fp are the CALENDAR quarter containing the period end, not the company's fiscal quarter. Each reply's `market_notes` and `schema` state the per-market caveats (solo or group accounts, lawful gaps, charities, flags in `form`). Detailed line items follow local accounting rules and keep the filed sign (capex is negative in Taiwan and Japan); get_data_dictionary defines them per market. The source licences require each reply's `attribution` and `licence` notices to accompany the figures.

NameTypeReqDescription
as_ofstring–Filing-date cut-off, YYYY-MM-DD: only filings dated on or before that day
compactboolean–true leaves out the long per-market notes (market_notes, schema) to save tokens; default false
fromstring–Earliest period end to include, YYYY-MM-DD
max_rowsinteger–Most rows to return, 1-250 (default 250); every metric keeps its most recent rows
metricstring–Comma-separated metrics, e.g. revenue,net_income
tickerstringyesTicker symbol, e.g. AAPL or 2330.TW

No output schema declared.

No examples provided.

get_group_structure ~221

A summary of one entity's place in the group-structure file (GLEIF relationship records, golden copy): whether the file holds a current direct and a current ultimate accounting consolidating parent for it, and how many current direct subsidiaries it has there, with the golden-copy date; for a US ticker, also how many subsidiaries the issuer lists in Exhibit 21 to its latest 10-K (SEC EDGAR, a count). Summary only, the same for every key: no names, LEIs, register numbers, periods or percentages; the reply says how the relationships themselves are supplied. The file covers relationships where the child or the parent has its legal address in the United States, the United Kingdom, Germany, France, Italy or Spain. Input: id, a ticker (e.g. FOXF, or a register-number ticker such as 493455042.FR) or a 20-character LEI.

NameTypeReqDescription
idstringyesA ticker (e.g. FOXF, 493455042.FR) or a 20-character LEI

No output schema declared.

No examples provided.

get_latest_fundamentals ~576

The most recent reported value of each metric for one ticker, each with its period (fy, fp), period end, filing date and form. Use it for a company's current figures, or with as_of for what had been filed by a given day. search_companies maps a company name to its ticker. Inputs: ticker (e.g. AAPL, 2330.TW, 005930.KS, 0403091220.BE, 775670417.FR, CC21860.NZC, and 10238429.EE, 5560356163.SE, 47239255.SK, 40003032949.LV where get_coverage lists them, and 96002925948.AU for Australia's tax figures); metric (comma-separated; a name we do not hold is listed in metrics_not_found); as_of (only filings dated on or before that day); compact (true leaves out market_notes and schema). Without a licence key, a company outside the full-history sample answers from its most recent reported fiscal year only (history_depth says so) and as_of is not available. Each metric is its own latest value, so two metrics can come from different periods; a quarterly fp is ONE quarter's figure, not a year; check `stale` (true: the company has filed since without this metric, so the figure is not current). Figures are as filed, each keyed to its filing date (`filed`) as its market records it (how each market dates a filing: https://www.tradingagentapp.com/fundamentals/methodology). .TW quarterly values are already SINGLE-QUARTER amounts, so differencing adjacent quarters gives wrong figures. For a quarterly row (US, Taiwan) fy and fp are the CALENDAR quarter containing the period end, not the company's fiscal quarter. Each reply's `market_notes` and `schema` state the per-market caveats (solo or group accounts, lawful gaps, charities, flags in `form`). Detailed line items follow local accounting rules and keep the filed sign (capex is negative in Taiwan and Japan); get_data_dictionary defines them per market. The source licences require each reply's `attribution` and `licence` notices to accompany the figures.

NameTypeReqDescription
as_ofstring–Filing-date cut-off, YYYY-MM-DD (e.g. 2022-01-01). Defaults to today.
compactboolean–true leaves out the long per-market notes (market_notes, schema) to save tokens; default false
metricstring–Comma-separated metrics, e.g. revenue,net_income. Omit for all.
tickerstringyesTicker symbol, e.g. AAPL or 2330.TW

No output schema declared.

No examples provided.

search_companies ~178

Look up the ticker for a company name or partial symbol — 'Apple', 'TSMC', '2330', 'samsung', 'LVMH'. Returns up to 8 matches, each with its ticker, name and market; a local subsidiary or a namesake in another country can share a name, and the market tells them apart. market (US, JP, TW, KR, FR, BE, DK, EE, SE, SK, LV, AU, NZC) limits the search to one market. Results with market NZC are New Zealand registered charities, not companies.

NameTypeReqDescription
marketstring–Only this market: US, JP, TW, KR, FR, BE, DK, EE, SE, SK, LV, AU, NZC
querystringyesCompany name or partial ticker

No output schema declared.

No examples provided.

Install

How do I install the Company fundamentals by filing date MCP server?

Company fundamentals by filing date is a hosted endpoint at https://www.tradingagentapp.com/api/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 · www.tradingagentapp.com

# add to Claude Code
claude mcp add --transport http wei-lienwu-pit-fundamentals 'https://www.tradingagentapp.com/api/mcp'
Common questions

What is the Company fundamentals by filing date MCP server?

Company fundamentals by filing date is an MCP server listed in the public MCP registry as io.github.Wei-LienWU/pit-fundamentals. Company financials from official filings, each figure keyed to its filing date. This page covers its hosted endpoint (https://www.tradingagentapp.com/api/mcp).

Is the Company fundamentals by filing date MCP server safe to use?

Company fundamentals by filing date scores 25 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 Company fundamentals by filing date MCP server expose?

Company fundamentals by filing date exposes 8 tools: get_latest_fundamentals, get_fundamentals_history, search_companies, get_coverage, get_data_dictionary, and 3 more. Their descriptions and schemas cost roughly 2,530 tokens of context every time the server is loaded.

Does the Company fundamentals by filing date MCP server require authentication?

Its publisher declares no required credentials for Company fundamentals by filing date. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Company fundamentals by filing date MCP server still maintained?

Company fundamentals by filing date 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 Company fundamentals by filing date MCP server?

VerifyMCP ran 5 checks on Company fundamentals by filing date, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Company fundamentals by filing date: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.