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.

io.github.kyliemckinleydemo/sec-filing-analyzer

REMOTE · WWW.STOCKHUNTR.NET

AI-analyzed SEC filings: filings, analysis, screening, 30-day signals, track record.

+1 this week 80 Trust /100

Last scanned (7 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 5 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 & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 552 tokens (~78/item across 7 items; 7 tools + 0 resources), lean.Pass
  • 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 Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% 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
  • We read all 7 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
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.

  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

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

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 · Probed https://www.stockhuntr.net/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.stockhuntr.net CN=YR2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 RSA 2048 SHA256-RSA 5a024664cf06c215bcebfb0253733ca50d6
SANs: www.stockhuntr.net
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.stockhuntr.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
stockhuntr.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.stockhuntr.net/api/mcp Verified 200
http (plaintext) http://www.stockhuntr.net/api/mcp HTTPS enforced 308 https://www.stockhuntr.net/api/mcp
MCP tools · 7 exposed · ~552 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_company ~47

Return a company snapshot (financials, valuation, analyst data) and its most recent analyzed SEC filings by ticker.

NameTypeReqDescription
tickerstringyesStock ticker, e.g. "MSFT"

No output schema declared.

No examples provided.

get_filing_analysis ~77

Return the full AI analysis for a single SEC filing by accession number: executive summary, concern level, sentiment, EPS surprise, predicted 30-day alpha, and (if available) the realized outcome.

NameTypeReqDescription
accession_numberstringyesSEC accession number, dashed form e.g. "0000320193-24-000123"

No output schema declared.

No examples provided.

get_latest_filings ~86

Return the most recent SEC filings (10-K, 10-Q, 8-K) with AI analysis and 30-day alpha predictions. Optionally filter by ticker and/or form type.

NameTypeReqDescription
filing_typestring–SEC form type
limitinteger–Max filings to return
tickerstring–Stock ticker, e.g. "AAPL"

No output schema declared.

No examples provided.

get_model_track_record ~49

Return the model's validated track record from strict 90-day walk-forward cross-validation, plus a live count of filings in the database that already have a realized 30-day outcome available for evaluation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_top_signals ~56

Return the highest-conviction filing predictions from the last 90 days, ranked by |predicted 30-day alpha| weighted by confidence. These are the model's strongest current directional calls.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

screen_companies ~189

Filter the tracked-company universe (800+ US companies, all S&P 500 constituents) by fundamentals: sector, minimum market cap, maximum P/E, minimum dividend yield, and minimum revenue growth. Mirrors the /screener tool. Returns matching companies with links to their pages.

NameTypeReqDescription
limitinteger––
max_penumber–Maximum trailing P/E ratio
min_dividend_yield_pctnumber–Minimum dividend yield in percent, e.g. 3 for 3%
min_market_cap_billionsnumber–Minimum market cap in USD billions
min_revenue_growth_pctnumber–Minimum TTM revenue growth in percent, e.g. 20 for 20%
sectorstring–Exact sector name, e.g. "Information Technology", "Financials", "Energy"
sortstring–Sort order

No output schema declared.

No examples provided.

search_companies ~48

Search tracked companies by ticker or name. Returns matching tickers with company names and sectors.

NameTypeReqDescription
limitinteger––
querystringyesTicker prefix or company name fragment

No output schema declared.

No examples provided.

Install

How do I install the io.github.kyliemckinleydemo/sec-filing-analyzer MCP server?

io.github.kyliemckinleydemo/sec-filing-analyzer is a hosted endpoint at https://www.stockhuntr.net/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.stockhuntr.net

# add to Claude Code
claude mcp add --transport http kyliemckinleydemo-sec-filing-analyzer 'https://www.stockhuntr.net/api/mcp'
Common questions

What is the io.github.kyliemckinleydemo/sec-filing-analyzer MCP server?

io.github.kyliemckinleydemo/sec-filing-analyzer is an MCP server listed in the public MCP registry as io.github.kyliemckinleydemo/sec-filing-analyzer. AI-analyzed SEC filings: filings, analysis, screening, 30-day signals, track record. This page covers its hosted endpoint (https://www.stockhuntr.net/api/mcp).

Is the io.github.kyliemckinleydemo/sec-filing-analyzer MCP server safe to use?

io.github.kyliemckinleydemo/sec-filing-analyzer scores 80 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 io.github.kyliemckinleydemo/sec-filing-analyzer MCP server expose?

io.github.kyliemckinleydemo/sec-filing-analyzer exposes 7 tools: get_latest_filings, get_filing_analysis, get_company, search_companies, screen_companies, and 2 more. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.

Does the io.github.kyliemckinleydemo/sec-filing-analyzer MCP server require authentication?

No. We connected to io.github.kyliemckinleydemo/sec-filing-analyzer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.kyliemckinleydemo/sec-filing-analyzer MCP server still maintained?

io.github.kyliemckinleydemo/sec-filing-analyzer 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.