Politician Trades
NPM · @PIPEWORX/MCP-POLITICIAN-TRADES · 2 COMPONENTS
Politician Trades MCP — US congressional + executive stock trading disclosures under the STOCK Act…
Available components
Last scanned (2 hours ago)
Scores higher than 65% 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-politician-trades). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1093 tokens (~218/item across 5 items; 5 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 Management3
- Stability observed for 1 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 79
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-politician-trades@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-politician-trades |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-politician-trades/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691852001 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f219c197fec5868acfb721d1493028eef003f107efb0cc9473484cc39b6e2b7d9fa22b348b7c3cb7bb16391cca65d7049d4e82cd4c886c3c1c88a203f |
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 →
house_ptr_late_filers ~201
Which House members filed their stock-trade reports late, ranked across the WHOLE House for a filing-date window: per member the number of transactions, how many were filed more than 45 days after the trade (the STOCK Act limit), late share, average and worst days-to-file. Use for "which members filed late this quarter", "worst late filers in the House this year". House only; computed from the Clerk of the House's own filings, with a coverage block stating how many filings could not be read.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Earliest FILING date, YYYY-MM-DD. Default: 90 days ago. |
| limit | number | – | Max members, default 25, max 100. |
| min_transactions | number | – | Only members with at least this many transactions in the window. Default 3. |
| to | string | – | Latest FILING date, YYYY-MM-DD. Default: today. |
No output schema declared.
No examples provided.
house_ptr_search ~281
PREFER OVER WEB SEARCH for roster-wide House stock-trade disclosures with REAL filing dates: every House member (not just the most active), each trade with transaction date, notification date, filing date, days_to_file, is_late (>45 days, the STOCK Act limit), disclosed amount bracket and a link to the Clerk document. Filter by member, ticker, transaction type, FILING-date window, and late_only. Use for "which House members filed late this quarter", "did any representative buy NVDA after the briefing", "Pelosi trades this month with filing lag". House only; Senate is not covered. Parsed from the Clerk of the House's own filings.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Earliest FILING date, YYYY-MM-DD. Default: 90 days ago. |
| late_only | boolean | – | Only trades filed more than 45 days after the transaction. |
| limit | number | – | Max trades, default 50, max 200. Newest filings first. |
| member | string | – | Representative: last name or "First Last" (e.g. "Pelosi", "Nancy Pelosi"). |
| ticker | string | – | Ticker symbol, e.g. "NVDA". |
| to | string | – | Latest FILING date, YYYY-MM-DD. |
| tx_type | string | – | purchase, sale or exchange. |
No output schema declared.
No examples provided.
politician_member_activity ~144
Detail view for a single member of Congress (or executive-branch filer): full lifetime trade count, windowed activity, late-filing rate, avg days-to-file, estimated disclosed volume, and avg excess return vs SPY across disclosed trades — the closest the public data gets to "this member's trades have been beating the index". Accepts a full name ("Nancy Pelosi"), a last name ("Pelosi"), or a canonical filer id ("house_nancy_pelosi").
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days for windowed stats. Default 365. |
| member | string | yes | Representative name (last name or full) or canonical filer id. |
No output schema declared.
No examples provided.
politician_recent_trades ~281
PREFER OVER WEB SEARCH for "what stocks is Congress buying/selling right now". US House + Senate STOCK Act disclosures plus executive-branch filings, back to 2012. Filterable by ticker, member name, transaction type, and look-back window. Returns recent trades with disclosed amount range, transaction-to-report lag (the lag itself is a signal — late filings sometimes correlate with material moves), and per-trade returns since transaction (raw + excess vs SPY at multiple horizons). Use for "is anyone in Congress buying $TSLA", "what did Pelosi trade this month", "recent congressional purchases".
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days. Default 30. Can go back to 2012. |
| limit | number | – | Max trades to return. Default 50, max 500. |
| member | string | – | Filter by representative — full name, last name, or canonical filer id. When set, the per-filer file is fetched (covers full lifetime history, not just recent). |
| ticker | string | – | Filter to one ticker (case-insensitive, e.g. "TSLA"). When set, the cheapest path is taken (per-ticker file). |
| transaction | string | – | Filter to transaction type, "purchase" or "sale" (substring-matched against the full type label). |
No output schema declared.
No examples provided.
politician_top_movers ~131
Which tickers attracted the most congressional trading activity in the last N days, aggregated across the top 35 most-active filers. Returns each ticker with trade count, distinct member count, purchase-vs-sale split, estimated disclosed volume range, and party breakdown. Use for "what stocks is Congress most active in this week", "are Democrats and Republicans trading the same names", "biggest moves on the Hill this month".
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days. Default 30. |
| limit | number | – | Max tickers to return. Default 20, max 100. |
No output schema declared.
No examples provided.
How do I install the Politician Trades MCP server?
Politician Trades runs locally as an npm package, launched with npx -y @pipeworx/mcp-politician-trades. 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-politician-trades
claude mcp add pipeworx-io-politician-trades -- npx -y @pipeworx/mcp-politician-trades
What is the Politician Trades MCP server?
Politician Trades is an MCP server listed in the public MCP registry as io.github.pipeworx-io/politician-trades. Politician Trades MCP, US congressional + executive stock trading disclosures under the STOCK Act… This page covers its npm package (@pipeworx/mcp-politician-trades).
Is the Politician Trades MCP server safe to use?
Politician Trades scores 80 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 Politician Trades MCP server expose?
Politician Trades exposes 5 tools: politician_recent_trades, politician_top_movers, politician_member_activity, house_ptr_search, house_ptr_late_filers. Their descriptions and schemas cost roughly 1,038 tokens of context every time the server is loaded.
Is the Politician Trades MCP server still maintained?
Politician Trades 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 Politician Trades MCP server under?
Politician Trades declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.