{"name":"downstream-fedreg","version":"0.1.0","transport":"streamable-http (JSON responses; no server-initiated stream)","protocol_versions":["2025-06-18","2025-03-26","2024-11-05"],"authentication":"none","how_to_connect":"Add https://mcp.downstream.sh as an MCP server, or POST JSON-RPC 2.0 to it directly. No key, no account.","endpoint":"https://mcp.downstream.sh/mcp","archive_origin":"https://downstream.sh","tools":[{"name":"get_daily_digest","description":"What the Federal Register published on one day: counts by document type, the dated obligations it created, and the documents that met a stated salience rule. Built from a hashed capture, so the answer is reproducible and carries the hash. Accepts a historical as_of. Returns nothing for a day the archive does not hold rather than guessing."},{"name":"whats_new_since","description":"Everything the Federal Register published between two dates, from the dated archive. Optionally filtered to an agency or to document types. This is the \"what did I miss\" call; it reads stored copies, so every item carries the capture it came from."},{"name":"catalyst_calendar","description":"One dated timeline across both branches: comment deadlines and effective dates the Federal Register created (certainty \"statutory\" — a date printed in a published document), and weeks the House scheduled a measure for floor consideration (certainty \"scheduled\" — the House can and does revise its own schedule). Every event says which branch it came from and how certain that kind of date is. Co-occurrence in a window is NOT a causal link: this shows both things happening, never that one caused the other."},{"name":"search_federal_register","description":"Full-text search of the Federal Register, live. Current to the minute and not a dated citation — responses are marked live and carry no content hash. Cannot be combined with a historical as_of; the server refuses rather than answering from the wrong corpus."},{"name":"get_document","description":"One Federal Register document by its document number (e.g. 2026-17001), live, with its dates, agencies, CFR references, docket ids and the official PDF URL."},{"name":"get_floor_week","description":"What the House may take up in one week, from its own published schedule: every measure, the procedural posture it is listed under (suspension of the rules, pursuant to a rule), and the sponsor where that record has been retrieved. Built from a hashed capture. A week the House published no schedule for is answered as a confirmed absence — usually recess — not as an empty week."},{"name":"search_measures","description":"Search every measure the House has scheduled across all weeks held — by the state a sponsor or cosponsor represents, by a member’s bioguide id, by procedural posture, or by text in the measure title. This is the delegation question: what has been on the floor that someone from my state put their name on. It reports who is on the record, and nothing about what anyone should do about it."},{"name":"search_presidential_documents","description":"Search the presidential corpus — memoranda, executive orders, proclamations — by text, by the White House’s own category, or by whether the Federal Register ever printed the document. This is the question the Register alone cannot answer: a presidential memorandum has no number and no series, publication is ordered by the President rather than required, and roughly a quarter of them are never printed at all. Each document carries a doc_uid derived from its own text, so the same document is one record no matter which publisher rendered it, and every cross-publisher link states the method that produced it rather than asserting a match."},{"name":"get_presidential_document","description":"One presidential document by its doc_uid, with every publisher’s rendering of it: the whitehouse.gov posting, the Federal Register printing where there is one, and the identity that ties them together. Reports whether the two published texts are byte-identical after normalization — when they are not, two arms of the government have published the same document differently, which is a fact this server reports rather than resolves."}],"daily":"https://downstream.sh/daily/","docs":"https://downstream.sh/essays/a-country-that-can-see.html"}