Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Congress Trade Alerts is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Congressional stock-trade disclosures (House + Senate PTRs) with each filing's lateness vs 45 days
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http congress-trade-alerts-mcp https://congresstradealerts.com/mcp
# 2 — ask your agent for something these tools do
# get_committee_trading, get_member_trades, get_top_traders and 9 more
Congress Trade Alerts costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 1 server
congresstradealerts1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http congress-trade-alerts-mcp https://congresstradealerts.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
For a given congressional committee, returns which members traded stock in the last N days, their trade counts, and the percentage of the committee that traded.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| committee_name | string | yes | Committee name or partial match, e.g. "Armed Services", "Finance" |
| days | integer | no | Look-back window in days, measured on trade date (default 90). Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of any window is incomplete. |
Returns stock trades disclosed by one member of Congress, newest trade first, with optional ticker and date-window filters. member_name must exactly match the member name as stored: the STOCK Act filer name with honorifics removed, which is often a legal name rather than the name the member is commonly known by. A name that does not match returns count 0 and no error, so resolve a common or partia
| Parameter | Type | Required | Notes |
|---|---|---|---|
| member_name | string | yes | Exact stored member name, e.g. "Nancy Pelosi"; look it up with search_members_and_tickers |
| ticker | string | no | Filter to a specific ticker symbol, e.g. "NVDA" |
| days | integer | no | Only trades whose trade date is within the last N days. Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of the window is incomplete. |
| limit | integer | no | Max trades to return (default 50) |
Returns the most active stock traders in Congress by trade count, optionally filtered by chamber (House or Senate) and date window.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chamber | string | no | Filter by chamber |
| days | integer | no | Look-back window in days, measured on trade date (default 90). Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of any window is incomplete. |
| limit | integer | no | Number of traders to return (default 10) |
Get recent congressional stock trades with optional filters for politician, ticker, party, chamber, and transaction type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| politician | string | no | Case-insensitive partial match on the member name, e.g. "Pelosi" |
| ticker | string | no | Filter by ticker symbol |
| party | string | no | Filter by party |
| chamber | string | no | Filter by chamber |
| tx_type | string | no | Filter by transaction type |
| limit | integer | no | Max results |
Returns a trading profile for one member of Congress: total trades, buys and sells, first and last trade dates, average disclosure lag, party, chamber, state, and committee assignments. member_name must exactly match the stored member name (the STOCK Act filer name with honorifics removed, often a legal name); a name that does not match returns total_trades 0 and no error, so resolve names with se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| member_name | string | yes | Exact stored member name, e.g. "Tommy Tuberville"; look it up with search_members_and_tickers |
Get all congressional trades for a specific stock ticker symbol.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. "AAPL" |
| days | integer | no | Look-back window in days, measured on trade date. Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of any window is incomplete. |
| limit | integer | no | Max results |
Get every Congress member who bought a specific ticker in the last N days, aggregated per politician.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. "NVDA" |
| days | integer | no | Look-back window in days, measured on trade date. Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of any window is incomplete. |
Get the most-traded stock tickers by Congress in the last N days. Set tx_type='Purchase' for most-bought tickers, or tx_type='Sale' for most-sold. Omit tx_type to rank on all trades (default).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Look-back window in days, measured on trade date. Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of any window is incomplete. |
| limit | integer | no | Max results |
| tx_type | string | no | Filter by transaction type: "Purchase" = buys only, "Sale" = sells only. Omit for all trades. |
Get trade counts broken down by party (D/R/I), with optional date filter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Look-back window in days, measured on trade date. Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of any window is incomplete. |
Get trade counts broken down by chamber (House vs Senate), with optional date filter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Look-back window in days, measured on trade date. Disclosures can arrive up to 45 days after the trade (later if filed late), so the newest part of any window is incomplete. |
Get high-level database stats: total trades (all-time + 30/60/90d), total members tracked, avg filing delay, sector breakdown.
No parameter schema on file.
Case-insensitive substring search over member names, ticker symbols, and company names. Returns up to limit matching members and up to limit matching tickers, each ordered by trade count. Use it to turn a common or partial name into the exact stored name that get_member_trades and get_member_profile require. A member who filed under several spellings appears once, under one of them, with trade
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query |
| limit | integer | no | Max results |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Congress Trade Alerts or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.1 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest7bfefa42083ebdb080e97686276ff163b6c04b0ad7c3c7babfdd49e069c8f1ce
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_committee_trading | no tags | |
| get_member_trades | no tags | |
| get_top_traders | no tags | |
| get_trade_feed | no tags | |
| get_member_profile | no tags | |
| get_trades_by_ticker | no tags | |
| get_ticker_buyers | no tags | |
| get_top_tickers | no tags | |
| get_party_breakdown | no tags | |
| get_chamber_breakdown | no tags | |
| get_aggregate_stats | no tags | |
| search_members_and_tickers | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7bfefa42083ebdb0
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Congress Trade Alerts can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.