cfr-compliance-mcp

A production-quality MCP (Model Context Protocol) server exposing the official eCFR (Electronic Code of Federal Regulations) API as structured tools, built for an AI-driven contract compliance pipeline.

Status: in active development. The MCP server's foundation, client, cache, and parsing layers are complete. Validation models, the 8 MCP tools, and the server entrypoint are still being built. See HANDOFF/PROJECT_HANDOFF.md for the full current status.

What this is

This package is the MCP server component of a larger pipeline:

Contract (PDF/DOCX) → Clause Extraction → Agno Team/Agents → this MCP Server
  → Official eCFR REST API → Relevant CFR Retrieval → Compliance Reasoning
  → Clause-wise Compliance Report

It has no dependency on any third-party MCP server — it talks directly to the official, public, unauthenticated eCFR REST API (https://www.ecfr.gov). See HANDOFF/PROJECT_HANDOFF.md Section 9 and the research addendum for why.

Related MCP server: Enterprise Financial Compliance Audit Framework

Requirements

• Python 3.12

• uv for dependency management

Setup

git clone <this repo>
cd cfr-compliance-mcp
uv sync
cp .env.example .env   # adjust settings if needed; defaults work out of the box

Running (once server.py exists)

uv run cfr-compliance-mcp

Project layout

src/cfr_compliance_mcp/
├── config.py, logging_config.py, exceptions.py, constants.py   # foundation
├── clients/        # generic HTTP transport + eCFR-specific API client
├── cache/          # backend-agnostic caching (in-memory today, Redis-ready)
├── parsing/        # raw eCFR XML -> clean text + citation metadata
├── models/         # (pending) Pydantic request/response validation
├── tools/          # (pending) the 8 MCP tools
└── server.py        # (pending) FastMCP entrypoint

Full architectural rationale is in HANDOFF/ARCHITECTURE.md. Chronological build history is in HANDOFF/PROJECT_PROGRESS.md. A single authoritative current-state reference (what's built, why, what's next) is HANDOFF/PROJECT_HANDOFF.md — read that first if you're picking this project up.

Testing

uv run pytest

(Test suite is not yet built — see HANDOFF/PROJECT_HANDOFF.md for status.)

Development conventions

• Full type hints, strict mypy.

• ruff for linting (uv run ruff check .).

• All configuration via .env / config.Settings — never os.environ directly.

• All logging via logging_config.get_logger(__name__) — logs go to stderr only (the MCP stdio transport uses stdout for the protocol itself; never write there).

• See HANDOFF/PROJECT_HANDOFF.md Section 17 for the full conventions list.