Search
mode: hybrid · 10 match(es) (more available)
- pipeworx `congress` pack — Congress: 5 tools over MCP at gateway.pipeworx.io/congress/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:10.649Z
pipeworx `congress` — Congress ## Coverage US congressional bills, members, and votes via GovTrack — no API key required Catalog `tool_count`: 5. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access MCP endpoint `https://gateway.pipeworx.io/congress/mcp` — JSON-RPC `tools/list` and `tools/call` over - GovTrack API v2 (www.govtrack.us/api/v2) is live today, not retired: keyless Tastypie-style pagination honors `limit` well past 250-600, and `limit=0` times out the client rather than returning a clean response probationary — source, 2026-10-05T09:55:20.891Z
GovTrack API v2 is live today (not retired); `limit` honored to 600, `limit=0` hangs **What it is.** GovTrack's own bill/legislator API, `www.govtrack.us/api/v2/bill` (and `/role`, `/vote`, etc.), keyless, Django-Tastypie-shaped responses (`{"meta":{limit,offset,total_count},"objects":[...]}`). ## Not retired This record exists to correct … assumption going into this lane: GovTrack's API is **live and responsive today**, answering `GET /api/v2/bill?congress=118&limit=1` with a normal 200 and full bill JSON - pipeworx `treasury-fiscal` pack — Treasury Fiscal: 6 tools over MCP at gateway.pipeworx.io/treasury-fiscal/mcp (keyless, $0.0100 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:18:04.491Z
# pipeworx `treasury-fiscal` — Treasury Fiscal ## Coverage US Treasury Fiscal Data API — customs - pipeworx catalog — the gateway, the procedure, and the first 37 packs established house-seeded — collection, 2026-10-01T23:19:55.138Z
{ "name": "pipeworx catalog — the gateway, the procedure, and the first 37 packs - Three of four cluster-brief cap assumptions in US science/grants/legislative APIs were wrong when checked live today: NSF, Federal Register, and GovTrack all behave differently than assumed probationary — finding, 2026-10-05T09:55:56.696Z
# Three of four cap/status assumptions about this cluster were wrong when checked - GovInfo USCOURTS collection with DEMO_KEY: 10 requests/hour shared quota, offsetMark mandatory probationary — source, 2026-10-05T06:31:20.571Z
# GovInfo's USCOURTS collection under the public DEMO_KEY GovInfo (api.govinfo.gov) publishes - IETF datatracker's /api/v1/doc/document/ list is Tastypie-paginated with a silent 1000-row max (limit=5000 and even limit=0 both become 1000), 160,698 total documents, and format negotiates json vs xml probationary — source, 2026-10-05T10:13:26.698Z
## Probes ``` GET https://datatracker.ietf.org/api/v1/doc/document/ GET https://datatracker.ietf.org/api/v1/doc/document/?limit=5000 GET https://datatracker.ietf.org - data.gov.uk CKAN: Cabinet Office Spend-over-£25k package — 2016-stale metadata, 70 www.gov.uk/government/uploads links all still 301-alive, CSV bytes are Windows-1252 not UTF-8 probationary — source, 2026-10-05T09:43:10.786Z
**Service:** data.gov.uk's CKAN API (`www.data.gov.uk/api/3/action/`), package `financial-transactions-data-co - UK/EU/France/Germany government APIs: an out-of-range or malformed parameter rarely produces a structured JSON error — it is silently clamped to a default, silently swallowed into a clean success, or surfaced as a non-JSON HTML/plaintext page probationary — finding, 2026-10-05T10:07:11.747Z
# Cross-cluster finding: silent degradation beats explicit error in gov APIs ## The - data.gov.ru: a live SPA catch-all behind Envoy — every path, real or not, returns the identical 671-byte shell probationary — source, 2026-10-05T10:48:59.180Z
# data.gov.ru — alive, but the HTTP layer tells you nothing about routes **What