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.

Bargo Congress Trades

REMOTE · WWW.BARGO.AI

Query normalized U.S. Congress STOCK Act trades with member, ticker, and performance data.

Available components

0 this week 85 Trust /100

Last scanned (23 hours ago)

Scores higher than 90% 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 Security83
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 282 tokens (~94/item across 3 items; 3 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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 3 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

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.bargo.ai/free-apis/congress/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bargo.ai CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 aa195cf5e5d99b771381b457c18b7518
SANs: bargo.ai, www.bargo.ai, *.www.bargo.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.bargo.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814, 3799 8, 8 Verified
bargo.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.bargo.ai/free-apis/congress/mcp Verified 200
http (plaintext) http://www.bargo.ai/free-apis/congress/mcp HTTPS enforced 301 https://www.bargo.ai/free-apis/congress/mcp
MCP tools · 3 exposed · ~282 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_congress_member ~74

All disclosed trades for one member of Congress plus a performance summary (trade count, buys/sells, average per-share return on disclosed buys). Pass the member_slug returned by get_congress_trades (e.g. 'nancy-pelosi').

NameTypeReqDescription
limitinteger––
member_slugstringyes–

No output schema declared.

No examples provided.

get_congress_stats ~48

Aggregate Congress-trading stats: total trades/members/tickers, buy vs sell counts, latest transaction & disclosure dates, and the most-traded tickers over the last 90 days.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_congress_trades ~160

U.S. Congress stock trades from official STOCK Act Periodic Transaction Reports (House Clerk + Senate eFD). Each row: member, chamber, state, ticker, company, type (purchase/sale/exchange), disclosed dollar range, transaction & disclosure dates, AND per-trade performance (price at trade, latest price, % move since). Filter by ticker, member (substring), chamber, or type. Newest transaction first. CAVEAT: PTRs are disclosed up to ~45 days after the trade — read as 'recent weeks', not real-time.

NameTypeReqDescription
chamberstring––
limitinteger––
memberstring––
tickerstring––
typestring––

No output schema declared.

No examples provided.

Install

How do I install the Bargo Congress Trades MCP server?

Bargo Congress Trades is a hosted endpoint at https://www.bargo.ai/free-apis/congress/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.bargo.ai

# add to Claude Code
claude mcp add --transport http bargo-ai-congress-trades 'https://www.bargo.ai/free-apis/congress/mcp'
Common questions

What is the Bargo Congress Trades MCP server?

Bargo Congress Trades is an MCP server listed in the public MCP registry as io.github.bargo-ai/congress-trades. Query normalized U.S. Congress STOCK Act trades with member, ticker, and performance data. This page covers its hosted endpoint (https://www.bargo.ai/free-apis/congress/mcp).

Is the Bargo Congress Trades MCP server safe to use?

Bargo Congress Trades scores 85 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 Bargo Congress Trades MCP server expose?

Bargo Congress Trades exposes 3 tools: get_congress_trades, get_congress_member, get_congress_stats. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.

Does the Bargo Congress Trades MCP server require authentication?

Yes. Bargo Congress Trades asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Bargo Congress Trades MCP server still maintained?

Bargo Congress 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 did VerifyMCP test on the Bargo Congress Trades MCP server?

VerifyMCP ran 13 checks on Bargo Congress Trades, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.