Fca Shorts
NPM · @PIPEWORX/MCP-FCA-SHORTS · 2 COMPONENTS
FCA UK short-position disclosures — the Financial Conduct Authority (fca.org.uk) publishes a daily…
Available components
Last scanned (5 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-fca-shorts). 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 570 tokens (~190/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 4 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 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-fca-shorts@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-fca-shorts |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fca-shorts/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635937414 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:84dc32056dce7aa02f63cd2a979227ac67a2e600394a68c1457516803e1d8e982952dc93f3b887bdcc92618468fe6dc8f12c22de9c0bb5cb34119b913 |
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 →
fca_largest_shorts ~106
The N issuers with the largest currently FCA-disclosed net short positions market-wide, sorted descending by aggregated position %. Reads the same daily "aggregated-current-net-short-positions" file as fca_short_positions -- aggregated per issuer, no holder names. Example: fca_largest_shorts({ top_n: 10 }).
| Name | Type | Req | Description |
|---|---|---|---|
| top_n | number | – | How many issuers to return, most-shorted first. Default 20, max 100. |
No output schema declared.
No examples provided.
fca_short_changes ~229
Per-issuer short-position deltas: compares each issuer's latest CURRENT disclosed position against the most recent prior value shown for that ISIN in the HISTORIC disclosures file, i.e. what moved and by how much since the previous reported position. Filter to one issuer/ISIN, or omit both to get the largest market-wide moves (optionally only since a given date). Example: fca_short_changes({ isin: "GB00B01QGK86" }) or fca_short_changes({ since: "2026-09-15", top_n: 15 }).
| Name | Type | Req | Description |
|---|---|---|---|
| isin | string | – | Exact ISIN to restrict to. |
| issuer | string | – | Issuer/company name substring (case-insensitive) to restrict to. |
| since | string | – | ISO date (YYYY-MM-DD). Only include issuers whose current position date is on or after this date. |
| top_n | number | – | When no issuer/ISIN filter is given, how many of the largest moves to return, ranked by absolute change. Default 20, max 100. |
No output schema declared.
No examples provided.
fca_short_positions ~179
Current FCA-disclosed net short position(s) for an issuer, from the daily "aggregated-current-net-short-positions" file (fca.org.uk). Data is AGGREGATED AND ANONYMISED PER ISSUER under the UK Short Selling Regulations 2025 -- one row per issuer, no position-holder names. Filter by issuer name (substring, case-insensitive) and/or ISIN; at least one is required. Example: fca_short_positions({ issuer: "Kingfisher" }) or fca_short_positions({ isin: "GB0033195214" }).
| Name | Type | Req | Description |
|---|---|---|---|
| isin | string | – | Exact ISIN, e.g. "GB0033195214". |
| issuer | string | – | Issuer/company name, or a substring of it (case-insensitive), e.g. "Kingfisher". |
No output schema declared.
No examples provided.
How do I install the Fca Shorts MCP server?
Fca Shorts runs locally as an npm package, launched with npx -y @pipeworx/mcp-fca-shorts. 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-fca-shorts
claude mcp add pipeworx-io-fca-shorts -- npx -y @pipeworx/mcp-fca-shorts
What is the Fca Shorts MCP server?
Fca Shorts is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fca-shorts. FCA UK short-position disclosures, the Financial Conduct Authority (fca.org.uk) publishes a daily… This page covers its npm package (@pipeworx/mcp-fca-shorts).
Is the Fca Shorts MCP server safe to use?
Fca Shorts 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 Fca Shorts MCP server expose?
Fca Shorts exposes 3 tools: fca_short_positions, fca_largest_shorts, fca_short_changes. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.
Is the Fca Shorts MCP server still maintained?
Fca Shorts 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 Fca Shorts MCP server under?
Fca Shorts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.