@blen/fedreg-mcp-server 2.0.0

package/CHANGELOG.md

@@ -0,0 +1,125 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and this project
+adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [2.0.0] - 2026-08-06
+
+**Breaking release.** The HTTP transport moves to the stateless MCP `2026-07-28`
+protocol and tool arguments are now strictly validated. Pre-2026 MCP clients
+keep working via a built-in legacy fallback. See the
+[v2 migration guide](docs/migration-v2.md) for client and operator upgrade
+steps.
+
+### Changed
+- **MCP protocol upgraded to `2026-07-28` (stateless core).** BREAKING for the
+  HTTP transport. The `initialize`/`initialized` handshake and the
+  `Mcp-Session-Id` header are gone; each request is self-contained, carrying its
+  protocol version, client info, and capabilities in `_meta`. Requests can now
+  be load-balanced across replicas with no sticky routing or shared session
+  store. Migrated from `@modelcontextprotocol/sdk@1.x` to the v2 SDK
+  (`@modelcontextprotocol/server` + `@modelcontextprotocol/node` `2.0.0`), which
+  is the release line implementing this revision.
+- **Per-subject quota attribution no longer depends on a session.** The
+  authenticated subject is re-derived from the caller's bearer token on every
+  request and passed to the tool catalog for that request only. This replaces
+  the 2025-era session-subject binding (and the `403 session_subject_mismatch`
+  guard added on `main` after v1.0.0, which never shipped in a release). The
+  binding existed to stop one tenant reusing another's session id to spend
+  or pollute their quota — an attack with no carrier now that no session id
+  exists.
+- **Tool arguments are now validated against the advertised JSON Schema.**
+  BREAKING for clients that sent extra argument keys. `registerTool` attaches the
+  SDK's validator, and the generated schemas set `additionalProperties: false`, so
+  an unrecognized key returns `isError: true` with `"Input validation error: …
+  must NOT have additional properties"`. Under `1.x` the schema was advertisement
+  only and Zod silently stripped unknown keys.
+- **An unknown tool name is now a JSON-RPC error, not a tool result.** It returns
+  `{"error":{"code":-32602,"message":"Tool X not found"}}` instead of the previous
+  `isError: true` content block, so clients must not read `result.isError` to
+  detect it.
+- **Per-source corpora** — the merged `schema/field-dictionary.json` is now
+  split into per-source files (`schema/{fr,ecfr,regs}.json`), each loaded by
+  its own `Source` via a registry (`getSources`).
+
+### Added
+- `server/discover` — advertises supported protocol versions, capabilities, and
+  server identity on demand, replacing what the handshake used to carry.
+- On modern (`2026-07-28`) requests the `Mcp-Method` routing header is
+  required — plus `Mcp-Name` for `tools/call` — and is validated against the
+  request body; a missing or disagreeing header is rejected with `-32020`
+  (`HeaderMismatch`). Legacy requests are unaffected.
+- `tools/list` and `server/discover` results carry `ttlMs` (300 s) and
+  `cacheScope: "public"`. The catalog derives only from process configuration,
+  never from the caller, so it is identical for every tenant and safe to share.
+- Backward compatibility for pre-2026 clients: requests without the `_meta`
+  envelope are classified as legacy and answered by a per-request stateless
+  `2025-11-25` fallback, so the `initialize` handshake keeps working. No session
+  is minted on either path.
+
+- **regulations.gov source** — a third SDK binding, `regs.*`
+  (`documents`, `comments`, `dockets`, each with `search` / `get`), exposing
+  public comments, dockets, and live comment-period status. Requires a free
+  API key (`FEDREG_REGS_API_KEY`); the key is held host-side and never reaches
+  the sandbox. Without it, `regs` is disabled (`SourceUnavailable`) while `fr`
+  and `ecfr` keep working. Configurable via `FEDREG_REGS_BASE_URL` and a
+  per-`execute()` upstream-call budget (`FEDREG_REGS_MAX_CALLS_PER_EXECUTE`,
+  default 30).
+- **regulations.gov rate guardrails** — to protect the shared api.data.gov key:
+  a process-wide hourly token bucket (`FEDREG_REGS_RATE_PER_HOUR`, default 1000;
+  in-memory, so it does not coordinate across replicas), a per-authenticated-subject
+  hourly quota in HTTP mode (`FEDREG_REGS_SUBJECT_RATE_PER_HOUR`, default 500), and
+  no-429-retry on `regs`. The GET response cache key now also incorporates a redacted
+  auth-context hash (no cross-key cache bleed), and the per-subject quota is keyed on
+  the subject the request's own bearer token verified as.
+
+### Removed
+- `FEDREG_MAX_SESSIONS` — there are no protocol sessions left to cap. An existing
+  deployment that still sets it is silently ignored rather than erroring.
+- `GET`/`DELETE` on `/mcp` (2025-era session operations) now return `405`.
+- `subscriptions/listen` is refused (`maxSubscriptions: 0`). This server declares
+  only the `tools` capability, but the SDK routes the method regardless and would
+  otherwise hold up to 1024 long-lived SSE streams per handler — the unbounded
+  long-lived state that `FEDREG_MAX_SESSIONS` used to cap.
+
+## [1.0.0] - 2026-05-20
+
+Initial public release.
+
+### Added
+- **Three-tool code-mode MCP surface** — `search_api`, `describe_schema`,
+  `execute` (the same pattern as `clinicaltrials-mcp-server`).
+- **SDK bindings** — `fr.*` for FederalRegister.gov v1 (`documents`,
+  `publicInspection`, `agencies`, `issues`, `suggestedSearches`, `images`)
+  and `ecfr.*` for the Electronic Code of Federal Regulations (`titles`,
+  `admin.agencies`, `structure`, `ancestry`, `versions`, `full`, `search.*`).
+- **BM25 search** over a curated endpoint + field dictionary
+  (`schema/field-dictionary.json`).
+- **Sandbox** — `isolated-vm` (primary) and Deno subprocess (fallback) with
+  shared AST preflight via `acorn`, wall-clock timeout, and heap cap.
+- **stdio transport** for Claude Desktop and MCPB.
+- **Streamable HTTP transport** built on `@modelcontextprotocol/sdk` 1.29:
+  per-session `StreamableHTTPServerTransport`, SSE streaming, graceful
+  SIGTERM/SIGINT drain.
+- **OAuth 2.0 Protected Resource Metadata** per RFC 9728 at
+  `/.well-known/oauth-protected-resource/mcp`, `WWW-Authenticate` header
+  pointing at it on 401.
+- **Bearer token verification** via `jose` against any JWKS endpoint
+  (presets: `clerk`, `workos`, `auth0`, `generic-oidc`; `embedded` HS256
+  for dev).
+- **Hardening** — per-IP token-bucket rate limiting, per-subject daily
+  quotas, Host-header allowlist for DNS-rebinding protection.
+- **Deploy** — multi-stage Dockerfile (`deploy/Dockerfile`) that builds
+  `isolated-vm` and slims to a `node:22-bookworm-slim` runtime, plus a
+  Railway walkthrough in `deploy/RAILWAY.md`.
+- **27 tests** across BM25, sandbox policy, both SDK clients (vs `undici`
+  MockAgent), HTTP rate limiter, and an end-to-end MCP flow (initialize
+  → notifications/initialized → tools/list → tools/call → sandbox → SDK
+  → mocked upstream).
+
+[Unreleased]: https://github.com/blen-labs/fedreg-mcp-server/compare/v2.0.0...HEAD
+[2.0.0]: https://github.com/blen-labs/fedreg-mcp-server/compare/v1.0.0...v2.0.0
+[1.0.0]: https://github.com/blen-labs/fedreg-mcp-server/releases/tag/v1.0.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,15 @@
+@blen/fedreg-mcp-server
+Copyright 2026 BLEN, Inc.
+
+This product includes software developed at BLEN, Inc. (https://blenlabs.com).
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+This product fetches data from public U.S. government APIs:
+  - FederalRegister.gov API v1 (U.S. Government Publishing Office / National Archives)
+  - Electronic Code of Federal Regulations (eCFR) API
+  - Regulations.gov API v4 (U.S. General Services Administration / api.data.gov)

package/README.md

@@ -0,0 +1,219 @@
+# Federal Register MCP Server
+
+[![CI](https://github.com/blen-labs/fedreg-mcp-server/actions/workflows/ci.yml/badge.svg)](https://github.com/blen-labs/fedreg-mcp-server/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/@blen/fedreg-mcp-server.svg)](https://www.npmjs.com/package/@blen/fedreg-mcp-server)
+[![license: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](./LICENSE)
+[![Node](https://img.shields.io/badge/node-%E2%89%A520.10-339933.svg)](https://nodejs.org/)
+[![MCP](https://img.shields.io/badge/MCP-2026--07--28-7c3aed.svg)](https://modelcontextprotocol.io/specification/2026-07-28)
+
+<p align="center">
+  <video src="https://github.com/blen-labs/fedreg-mcp-server/raw/main/media/fedreg-launch.mp4" poster="https://raw.githubusercontent.com/blen-labs/fedreg-mcp-server/main/media/launch-poster.png" controls muted playsinline width="760"></video>
+</p>
+
+**Ask your AI assistant real questions about U.S. federal regulations — and get answers grounded in the official Federal Register, eCFR, and regulations.gov.**
+
+This is a [Model Context Protocol](https://modelcontextprotocol.io) server that connects any MCP client (Claude Desktop and others) to three official U.S. government sources:
+
+- **[Federal Register](https://www.federalregister.gov)** — the daily journal of the federal government: rules, proposed rules, notices, and presidential documents since 1994.
+- **[Electronic Code of Federal Regulations (eCFR)](https://www.ecfr.gov)** — the current, continuously updated text of the Code of Federal Regulations.
+- **[regulations.gov](https://www.regulations.gov)** — public comments, dockets, and live comment-period status for federal rulemakings.
+
+Instead of bolting on dozens of rigid, narrow tools, it hands the model a small, well-typed TypeScript SDK and lets it write the exact query it needs — then runs that code in a locked-down sandbox. This is the **code-mode** pattern, and it makes wide government APIs usable without overwhelming the model with tool definitions.
+
+> Independent open-source project. It calls public U.S. government APIs and is not affiliated with or endorsed by the U.S. government.
+
+## See it in action
+
+Ask Claude:
+
+> *"What does 50 CFR 21.150 cover, and have there been recent Federal Register rules touching migratory-bird depredation?"*
+
+The model finds the right calls and runs them in the sandbox — no hand-written tool per endpoint:
+
+```ts
+// Pull the current text of an eCFR section…
+const { titles } = await ecfr.titles.list();
+const date = titles.find(t => t.number === 50).latest_issue_date;
+const section = await ecfr.full(date, 50, { part: '21', section: '21.150' });
+
+// …and search the Federal Register for related rulemaking.
+const rules = await fr.documents.search({
+  conditions: { term: 'migratory bird depredation', type: ['RULE', 'PRORULE'] },
+  fields: ['title', 'publication_date', 'html_url'],
+  per_page: 5,
+  order: 'newest',
+});
+```
+
+…then answers in plain English, citing the section and the rules it found.
+
+## Features
+
+- **Three official sources, one server** — the full Federal Register v1 (`fr.*`), eCFR (`ecfr.*`), and regulations.gov v4 (`regs.*`) APIs behind one server.
+- **Code mode, not tool sprawl** — the model writes TypeScript against typed `fr` / `ecfr` / `regs` SDKs instead of juggling dozens of single-purpose tools.
+- **Safe by construction** — user code runs in an `isolated-vm` (or Deno) sandbox with **no network, filesystem, env, or subprocess access**. The only way out is to the three upstream government APIs.
+- **Runs anywhere MCP does** — stdio for Claude Desktop, or a remote Streamable HTTP server with OAuth, rate limiting, and quotas.
+- **Discovery built in** — `search_api` and `describe_schema` help the model (and you) find the right call fast.
+
+## Which source for what
+
+| Need | Source |
+|---|---|
+| Daily rules, proposed rules, notices; FR document metadata since 1994 | `fr` |
+| Current Code of Federal Regulations text | `ecfr` |
+| Public comments, dockets, live comment-period status | `regs` |
+
+For canonical Federal Register rule text and metadata since 1994, prefer `fr.documents` — regulations.gov documents overlap it. Reach for `regs` when you need what only it has: public **comments**, **dockets**, and live comment-period status.
+
+### regulations.gov API key
+
+regulations.gov requires a free API key from [api.data.gov / open.gsa.gov](https://open.gsa.gov/api/regulationsgov/). Set it via `FEDREG_REGS_API_KEY`. The key is held host-side and never reaches the sandbox.
+
+Without a key the `regs` source is **disabled** — `regs.*` calls return a clear `SourceUnavailable` error, while `fr` and `ecfr` keep working normally.
+
+Because the regulations.gov key is shared, `regs` upstream calls are bounded by a process-wide hourly bucket (`FEDREG_REGS_RATE_PER_HOUR`), a per-subject hourly quota in HTTP mode (`FEDREG_REGS_SUBJECT_RATE_PER_HOUR`; under `--insecure` all callers share the single `anonymous` bucket, and stdio skips it), and a per-`execute()` call budget (`FEDREG_REGS_MAX_CALLS_PER_EXECUTE`). For the two hourly rates, `0` is **not** "unlimited" — it blocks all regs calls; to disable regs entirely, leave `FEDREG_REGS_API_KEY` unset.
+
+### Bridge example: comments on a Federal Register rule
+
+`frDocNum` is a *returned* attribute on regs documents, not a filter — so bridge from FR to regulations.gov via the document number as a `searchTerm`:
+
+```ts
+// 1. Find the rule in the Federal Register and read its document number.
+const fr1 = await fr.documents.search({
+  conditions: { term: 'methane', type: ['RULE'] },
+  per_page: 1,
+  order: 'newest',
+});
+const docNum = fr1.results[0].document_number;
+
+// 2. Look it up on regulations.gov by document number, then read its objectId.
+const rd = await regs.documents.search({ filter: { searchTerm: docNum } });
+const objectId = rd.data[0].attributes.objectId;
+
+// 3. Pull the public comments filed on that document.
+const comments = await regs.comments.search({
+  filter: { commentOnId: objectId },
+  page: { size: 250 },
+});
+```
+
+## Quickstart (Claude Desktop)
+
+Add the server to your Claude Desktop config (**Settings → Developer → Edit Config**):
+
+```json
+{
+  "mcpServers": {
+    "fedreg": {
+      "command": "npx",
+      "args": ["-y", "@blen/fedreg-mcp-server"]
+    }
+  }
+}
+```
+
+Restart Claude Desktop, then just ask in plain language:
+
+> *"Find EPA methane rules published since 2024."*
+> *"What does 40 CFR Part 60 cover?"*
+> *"Which proposed rules opened for public comment this week?"*
+
+Requires **Node.js ≥ 20.10**. `npx` downloads and runs the server on demand; no global install needed. If the `execute` tool reports `SandboxUnavailable`, see [Sandbox runtimes](#sandbox-runtimes).
+
+## How it works
+
+Three tools, in the order the model uses them:
+
+| Tool | What it does |
+|---|---|
+| `search_api(query, k?)` | Finds the right endpoint/field via BM25 over the SDK docs. Returns ready-to-run TypeScript snippets. |
+| `describe_schema({ path? \| prefix? })` | Looks up an exact call or lists a whole namespace. |
+| `execute({ code, timeoutMs?, memoryMb? })` | Runs TypeScript in the sandbox, with `fr`, `ecfr`, and `regs` as globals. (`regs` is always defined; without `FEDREG_REGS_API_KEY` its calls return a `SourceUnavailable` error rather than a `ReferenceError`.) |
+
+A request flows from the MCP client through `execute` into the sandbox; the `fr.*` / `ecfr.*` / `regs.*` globals are thin proxies that marshal each call across a host-side RPC bridge to the real APIs:
+
+```text
+MCP client → execute(code) → sandbox → fr.* / ecfr.* / regs.* RPC bridge → upstream APIs
+```
+
+Full SDK surface: [`docs/sdk-reference.md`](./docs/sdk-reference.md) · Architecture: [`docs/architecture.md`](./docs/architecture.md) · Paste-ready examples: [`examples/`](./examples/).
+
+## Sandbox runtimes
+
+`execute` needs a sandbox runner. The server picks one automatically:
+
+1. **`isolated-vm`** (preferred) — a fresh V8 isolate. Built automatically during install on Linux/macOS/Windows (x64/arm64) where a C++ toolchain is present.
+2. **Deno** (fallback) — used when `isolated-vm` isn't available and `deno` is on `PATH`.
+3. If neither is available, `search_api` and `describe_schema` still work; `execute` returns `SandboxUnavailable`.
+
+> On very new Node majors, `isolated-vm` may not have a compatible prebuild yet. Install [Deno](https://docs.deno.com/runtime/getting_started/installation/) and run with `--sandbox deno` (or `FEDREG_SANDBOX=deno`). Node 20 and 22 build `isolated-vm` cleanly.
+
+## Self-hosting (remote HTTP)
+
+Run a shared, authenticated endpoint over Streamable HTTP:
+
+```bash
+# Dev only — no auth, loopback-bound:
+npx @blen/fedreg-mcp-server --http --insecure --host 127.0.0.1 --port 8080
+
+# Production — auth via any OIDC issuer:
+FEDREG_AUTH_PROVIDER=clerk \
+FEDREG_AUTH_ISSUER=https://<tenant>.clerk.accounts.dev \
+FEDREG_AUTH_JWKS_URL=https://<tenant>.clerk.accounts.dev/.well-known/jwks.json \
+FEDREG_PUBLIC_ORIGIN=https://your-host.example.com \
+FEDREG_ALLOWED_HOSTS=your-host.example.com \
+  npx @blen/fedreg-mcp-server --http
+```
+
+Then point any MCP client at it:
+
+```json
+{ "mcpServers": { "fedreg": { "type": "http", "url": "https://your-host.example.com/mcp" } } }
+```
+
+The HTTP transport implements the stateless MCP `2026-07-28` Streamable HTTP profile — no `initialize` handshake and no `Mcp-Session-Id`, so requests can be load-balanced across replicas without sticky routing. Pre-2026 clients are still served through a stateless legacy fallback. It adds OAuth 2.0 Protected Resource Metadata (RFC 9728), per-IP rate limiting, per-subject daily quotas, and Host-header allowlisting. A step-by-step Railway walkthrough is in [`deploy/RAILWAY.md`](./deploy/RAILWAY.md); the bundled [`Dockerfile`](./deploy/Dockerfile) precompiles `isolated-vm` and slims to a ~220 MB `node:22-bookworm-slim` runtime.
+
+### Configuration
+
+The most common knobs (full list and defaults in [`.env.example`](./.env.example)):
+
+| Variable | Default | Notes |
+|---|---|---|
+| `FEDREG_SANDBOX` | `auto` | `auto` / `isolate` / `deno` |
+| `FEDREG_USER_AGENT` | `fedreg-mcp-server/2.0 …` | Identify yourself, per FR/eCFR etiquette. |
+| `FEDREG_REGS_API_KEY` | — | Free key from regulations.gov / api.data.gov. Unset ⇒ `regs` disabled (fr/ecfr unaffected). |
+| `FEDREG_REGS_BASE_URL` | `https://api.regulations.gov` | regulations.gov v4 API base URL. |
+| `FEDREG_REGS_MAX_CALLS_PER_EXECUTE` | `30` | Caps regulations.gov upstream calls per `execute()` run (rate-limit guardrail). |
+| `FEDREG_REGS_RATE_PER_HOUR` | `1000` | Process-wide cap on regs upstream calls/hour (protects the shared key). In-memory; with N replicas, divide by N. Must be ≥ 1. |
+| `FEDREG_REGS_SUBJECT_RATE_PER_HOUR` | `500` | Per-subject regs calls/hour (HTTP mode only; skipped on stdio; one shared `anonymous` bucket under `--insecure`). Must be ≥ 1. |
+| `FEDREG_AUTH_PROVIDER` | `none` | `none` / `embedded` / `generic-oidc` / `clerk` / `workos` / `auth0` |
+| `FEDREG_PUBLIC_ORIGIN` | — | Public origin clients reach (used in OAuth metadata). |
+| `FEDREG_SUBJECT_DAILY_QUOTA` | `10000` | Requests per authenticated subject per UTC day. |
+
+CLI options: `--http`, `--port`, `--host`, `--sandbox auto|isolate|deno`, `--insecure`, `--help`.
+
+## Security
+
+User code is sandboxed by design — no network, filesystem, env, or subprocess access, an `acorn` AST preflight, a wall-clock timeout, and — on the `isolated-vm` runner — a heap cap (`memoryMb` is not enforceable on the Deno fallback). The full threat model is in [`SECURITY.md`](./SECURITY.md). Found a sandbox escape or auth bypass? Please open a [private Security Advisory](https://github.com/blen-labs/fedreg-mcp-server/security/advisories/new) rather than a public issue.
+
+## Contributing
+
+Contributions are welcome — see [`CONTRIBUTING.md`](./CONTRIBUTING.md) for the dev setup and ground rules, and please open an issue before anything non-trivial. By participating you agree to the [Code of Conduct](./CODE_OF_CONDUCT.md).
+
+## License
+
+[Apache-2.0](./LICENSE) © 2026 BLEN, Inc. See also [`NOTICE`](./NOTICE).
+
+## Acknowledgements
+
+- The U.S. Government Publishing Office and the National Archives for publishing the Federal Register and eCFR APIs.
+- The [Model Context Protocol](https://modelcontextprotocol.io) team for the spec and TypeScript SDK.
+- The teams who popularized the code-mode pattern for wide APIs.
+
+---
+
+## About BLEN
+
+BLEN, Inc is a digital services company that provides Emerging Technology (ML/AI, RPA), Digital Modernization (Legacy to Cloud), and Human-Centered Web/Mobile Design and Development.
+
+Built with ❤️ by [BLEN, Inc](https://www.blenlabs.com).

package/SECURITY.md

@@ -0,0 +1,99 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Please **do not file public GitHub issues for security reports**. Instead,
+open a private GitHub Security Advisory:
+
+> <https://github.com/blen-labs/fedreg-mcp-server/security/advisories/new>
+
+If that's not available, contact the maintainers via the GitHub organization
+page at <https://github.com/blen-labs>.
+
+We try to respond within **3 business days**. A typical timeline for a
+confirmed sandbox-escape report:
+
+1. Initial acknowledgement and severity triage — within 3 business days.
+2. Coordinated fix in a private branch — within 14 days for critical, 30 for
+   high-severity issues.
+3. Patched release published to npm with a credit line (unless you ask not
+   to be credited).
+4. Public advisory and CVE filing once users have had reasonable upgrade time.
+
+## Scope
+
+In scope:
+- **Sandbox escapes** — any code in `execute` that gets host filesystem,
+  network, environment, subprocess, native binding, or out-of-isolate
+  references.
+- **AST preflight bypasses** — code that passes `preflight()` in
+  `src/sandbox/policy.ts` but performs disallowed operations at runtime.
+- **Auth bypass** — sending requests to `/mcp` without a valid bearer that
+  reaches a tool handler.
+- **DNS rebinding / SSRF** against the HTTP transport.
+- **Quota / rate-limit bypass** that allows a single subject or IP to exceed
+  the configured ceiling.
+
+Out of scope (please file a normal issue instead):
+- Upstream API rate limits (those are FederalRegister.gov / eCFR /
+  regulations.gov limits; see the `FEDREG_REGS_*` guardrails in the README).
+- Denial of service via lawful but expensive queries (we accept this risk
+  on a per-tenant basis; tune `FEDREG_SUBJECT_DAILY_QUOTA` and
+  `FEDREG_IP_RPS`).
+- Issues that only occur with `--insecure` (which is documented as dev-only).
+
+## Sandbox guarantees
+
+The `execute` tool runs user-supplied TypeScript with two layered defenses:
+
+1. **AST preflight** (`acorn` + `acorn-walk`, see `src/sandbox/policy.ts`):
+   rejects `import` / `import()` / `eval` / `new Function` and references to
+   `process`, `globalThis`, `Buffer`, `Deno`, `fetch`, `Worker`, plus
+   `__proto__` / `constructor` / `prototype` member access. The check rejects
+   *static* uses of these names; runtime synthesis (e.g. via string
+   concatenation) is the next layer's job.
+2. **Runtime isolation** — one of:
+   - `isolated-vm`: a fresh V8 isolate, **no host references** other than
+     a single Reference to the RPC dispatcher; heap cap, wall-clock cap.
+   - `deno run --no-prompt <runner>`: subprocess with **no `--allow-*` flags**,
+     so no net/fs/env/ffi/subprocess access; wall-clock cap. The runner is a
+     temporary file so stdin stays free for the host RPC channel.
+
+Both runners deny network access to user code; the only way to reach
+upstream APIs is via the `fr.*` / `ecfr.*` / `regs.*` proxies, which serialize
+calls through a host-side RPC and execute them against the configured URL
+allowlist (`FEDREG_FR_BASE_URL`, `FEDREG_ECFR_BASE_URL`,
+`FEDREG_REGS_BASE_URL`).
+
+The regulations.gov API key (`FEDREG_REGS_API_KEY`) is held host-side in the
+`HttpClient` and is **never exposed to sandboxed user code**: it is injected
+into the upstream request on the host side of the RPC bridge, not passed into
+the sandbox, so user code cannot read or exfiltrate it.
+
+We treat any of the following as a vulnerability:
+- Reading the contents of any file under `/`.
+- Establishing any outbound socket to a host not configured in the SDK.
+- Reading process environment variables.
+- Reading or modifying host globals (this includes obtaining `globalThis`,
+  `Reflect`, `Function`, `eval`, or any constructor reachable from them).
+- Causing the host process to crash or hang past `timeoutMs * 2`.
+
+## Threat model
+
+This server is designed to be exposed to **untrusted MCP clients** behind
+an authenticated edge. Authentication is provided by an external OIDC issuer
+(Clerk / WorkOS / Auth0 / generic OIDC) and verified via JWKS. The HTTP
+transport adds Host-header allowlisting (DNS rebinding), per-IP token-bucket
+rate limiting, and per-subject daily quotas.
+
+This server is **not** designed to be a public unauthenticated endpoint.
+Operators who deploy with `--insecure` are explicitly opting out of all
+auth-layer protections and accept the resulting risk.
+
+## Dependencies
+
+We track advisories on direct runtime dependencies — `@modelcontextprotocol/server`,
+`@modelcontextprotocol/node`, `undici`, `jose`, `acorn`, `lru-cache`, `zod`, and the
+optional `isolated-vm`.
+For an advisory in any of these that affects this server, expect a patch
+release within the timeline above.