Finra
NPM · @PIPEWORX/MCP-FINRA · 2 COMPONENTS
FINRA short-sale data — Reg SHO daily short-sale VOLUME plus consolidated bi-monthly SHORT INTEREST.
Available components
Last scanned (7 hours ago)
Scores higher than 76% of npm servers
Category Finance and Payments
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-finra). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 685 tokens (~171/item across 4 items; 4 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 +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.
- 3 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.
- 1 Nov 26 0
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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 npm/@pipeworx/mcp-finra@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-finra |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-finra/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635943488 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:560fc663c97ea55df476d709f0b0c0aa1cb2f9bb1e4bb29146ea9aae3bdd5054c1d6ea5b98f88f47fb9eb6ea021c91991cee51557b61bf595cec3c22b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
short_interest ~152
FINRA consolidated SHORT INTEREST for one symbol — the bi-monthly settlement-date data: total open short position, days-to-cover, average daily volume, and change vs the prior settlement. This is the "% short / days-to-cover" metric investors cite — DISTINCT from short_volume_daily (daily short-sale VOLUME). Returns the latest settlement plus recent history, plus the FINRA attribution the data is licensed under. Zero-rated: FINRA's terms forbid charging for it, so this call costs 0 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many recent settlements to return (1–24, default 6) |
| symbol | string | yes | Ticker (case-insensitive), e.g. "TSLA" |
No output schema declared.
No examples provided.
short_volume_daily ~174
FINRA Reg SHO daily short-sale volume for one symbol on one trading day, summed across every consolidated-NMS reporting facility (Nasdaq TRF Carteret, NYSE TRF, Nasdaq TRF Chicago) so the total matches FINRA's consolidated CNMS figure. Returns short_volume, short_exempt_volume, total_volume, short_ratio (short / total), and the per-facility breakdown. Publishing lag is T+1 or better; omit `date` for the most recent published day. Zero-rated: FINRA's terms forbid charging for this data, so the call costs 0 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD or YYYYMMDD. Defaults to the most recent published trading day. |
| symbol | string | yes | Ticker (case-insensitive), e.g. "AAPL" |
No output schema declared.
No examples provided.
short_volume_history ~157
FINRA Reg SHO daily short-sale volume time series for one symbol — up to 30 trading days ending at `end_date` (default: most recent published day). Each day carries short_volume, short_exempt_volume, total_volume and short_ratio summed across every consolidated-NMS reporting facility, so the daily totals match FINRA's consolidated CNMS figures. Use it to see how a symbol's short-sale share of volume moved over recent sessions. Zero-rated: costs 0 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | 1–30 (default 10) |
| end_date | string | – | YYYY-MM-DD or YYYYMMDD; defaults to most recent published day |
| symbol | string | yes | Ticker (case-insensitive) |
No output schema declared.
No examples provided.
short_volume_top ~150
Ranks symbols on a given trading day by short_ratio (short_volume / total_volume) using FINRA Reg SHO daily data summed across every consolidated-NMS reporting facility. Scans the whole published day (~12,000 symbols) and returns the highest-ratio names. Useful for spotting heavily-shorted names; raise min_total_volume to exclude thinly-traded micro-caps. Zero-rated: costs 0 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD or YYYYMMDD; defaults to most recent published day |
| limit | number | – | 1–100 (default 25) |
| min_total_volume | number | – | Skip symbols below this consolidated total volume (default 100000) |
No output schema declared.
No examples provided.
How do I install the Finra MCP server?
Finra runs locally as an npm package, launched with npx -y @pipeworx/mcp-finra. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-finra
claude mcp add pipeworx-io-finra -- npx -y @pipeworx/mcp-finra
What is the Finra MCP server?
Finra is an MCP server listed in the public MCP registry as io.github.pipeworx-io/finra. FINRA short-sale data, Reg SHO daily short-sale VOLUME plus consolidated bi-monthly SHORT INTEREST. This page covers its npm package (@pipeworx/mcp-finra).
Is the Finra MCP server safe to use?
Finra scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Finra MCP server expose?
Finra exposes 4 tools: short_volume_daily, short_volume_history, short_volume_top, short_interest. Their descriptions and schemas cost roughly 633 tokens of context every time the server is loaded.
Is the Finra MCP server still maintained?
Finra 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 Finra MCP server under?
Finra declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.