us-congress-watch MCP Server

by nexlab Your server? Claim it

answering

us-congress-watch is answering right now. Last checked 4 min ago.

Monitor US bills

Uptime history 51 days of history · worst day 99%

51 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

984 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check us-congress-watch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add us-congress-watch --transport http https://mcp.nexlab.net/mcp/us-congress-watch

Settings → Connectors → Add custom connector, then paste this address

https://mcp.nexlab.net/mcp/us-congress-watch

~/.codex/config.toml

[mcp_servers.us-congress-watch]
url = "https://mcp.nexlab.net/mcp/us-congress-watch"

.cursor/mcp.json

{
  "mcpServers": {
    "us-congress-watch": {
      "url": "https://mcp.nexlab.net/mcp/us-congress-watch"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "us-congress-watch": {
      "type": "http",
      "url": "https://mcp.nexlab.net/mcp/us-congress-watch"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.nexlab.net/mcp/us-congress-watch	streamable-http	sign-in	891 ms	4 min ago

Alternatives to us-congress-watch

same job, measured the same way

Us Drought Monitor

by pipeworx-io

US Drought Monitor

44 tools answering

Europe Rail Watch MCP

by nexlab

Monitor European train stations

answering

EU Policy Watch MCP

by nexlab

Monitor EU policy across both law-making institutions

answering

Agent Watch

by entradox

Monitoring for the agent economy — liveness, latency, trust scoring for MCP endpoints

8 tools answering

Watch Engine

by alex-dev-web-c-de

Currency rates, VAT rates, and tariff rates via Watch Engine. 203 monitors.

3 tools answering

Water Quality Portal

by pipeworx-io

Water Quality Portal (WQP) MCP — US ambient water-chemistry monitoring

45 tools answering

CaseMagic — Federal Court Case Lookup & Monitor

by sustany

Free US federal court case lookup: status, judge, filings, deadlines. Then watch it for new filings.

17 tools answering

Competitor Monitor AI MCP

by csoai-org

Competitor Monitor Ai MCP Server by MEOK AI Labs

146 installs/wk local only

us-congress-watch — questions

Answers built from our own checks of this server.

Why is there no tool list for us-congress-watch?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is us-congress-watch working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 984 ms. The bar chart above shows every period we have measured.

How do I connect us-congress-watch?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to us-congress-watch?

No API key is involved. us-congress-watch answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is us-congress-watch?

It answers our handshake in 984 ms on average, which is faster than 6% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.