Overview
C4C: Mortgage Industry Regulations (Self-Hosted) is a container you run in your own AWS account, on Amazon ECS, AWS Fargate or Amazon EKS. It is a Model Context Protocol (MCP) server that gives your AI agents and assistants the actual text of U.S. mortgage regulations and agency guides: HUD Handbook 4000.1, the Fannie Mae Selling and Servicing Guides, the Freddie Mac Guide, the Ginnie Mae MBS Guide, the VA Lenders Handbook (M26-7) and USDA HB-1-3555, plus the CFR and U.S. Code sections they rest on.
Your agent calls C4C instead of answering guideline questions from memory or web search. It finds the governing section and returns it verbatim with the citation, effective date and dated source document, and flags rules with two versions in force, pending revisions or later changes. It resolves citations you already have (B3-4.3-04, 4000.1 II.A.4.c, 12 CFR 1026.43) and checks whether a quoted passage really appears in the regulator's text.
Built for security review: questions, documents and answers never leave your network through C4C. The container runs as non-root with a read-only root filesystem, needs no AWS credentials, and requires a bearer token you set. Its only outbound connection, if you use one at all, is an HTTPS download of signed library updates; every library is signature-checked before it is installed, and every answer reports the library version and age.
No external service is required. You choose where library updates come from: your own mirror (for example an S3 bucket in your account, read through a VPC gateway endpoint, with no license key and no connection to C4C), the C4C feed at mcp.claudeforcompliance.com (HTTPS, using a free license key from an automated sign-up with no approval step), or signed library files loaded offline.
Free. Licensed for research and reference use only. Results are not legal advice: verify against the primary source.
By CF Synergies, LLC.
Highlights
- Runs in your AWS account: questions and documents never leave your network through C4C; no AWS credentials needed; non-root, read-only filesystem, bearer-token auth.
- Verbatim text with citations, effective dates and version-in-force warnings, plus quote verification against the regulator's text.
- Signed, automatic library updates with version and age on every answer; offline loading for isolated networks. amd64 and Graviton (arm64).
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
This product is free. CF Synergies, LLC charges nothing for the software, so there is nothing to refund. AWS infrastructure charges for running it are billed by AWS under your AWS agreement. Questions: earl@cfsynergies.com .
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Amazon ECS / AWS Fargate (container image)
- Amazon ECS
- Amazon EKS
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
New: Amazon Bedrock AgentCore Runtime delivery option (MCP server). The AgentCore image has the signed regulation library built in (2026-10-25.2), listens on port 8000 with a /ping health check, and needs no license key or outbound connection; AgentCore handles caller authentication (IAM or OAuth). ECS and EKS images move to 1.1.0 with the same behavior as 1.0.2 plus a /ping endpoint. No breaking changes.
Additional details
Usage instructions
Research use only; results are not legal advice.
External services: none required. The container never sends questions, documents, answers or telemetry anywhere, and it refuses any library whose signature does not verify. Choose how library updates reach it: (a) your own mirror, such as an S3 bucket in your account read through a VPC gateway endpoint, so the container never contacts C4C and needs no license key; (b) directly from https://mcp.claudeforcompliance.com/library (HTTPS GET, port 443), sending only your free license key; or (c) offline, loading signed library files by hand.
Quickest install (about 10 minutes): launch the CloudFormation template from Deployment resources, or open https://us-east-1.console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/create/review?templateURL=https://c4c-marketplace-legal-046843662668.s3.amazonaws.com/c4c-ecs-fargate.yaml&stackName=c4c . It creates an ECS Fargate service in your private subnets behind an internal load balancer, generates the bearer token in AWS Secrets Manager (no one types it), and outputs the MCP endpoint and the command to read the token. The optional S3 mirror template creates a private bucket and gateway endpoint for updates through your own gates. Private subnets need a NAT gateway or VPC endpoints for ECR, Secrets Manager and CloudWatch Logs.
Manual install:
- Get a free license key at https://mcp-auth.claudeforcompliance.com/self-hosted (automated, no approval). With your own mirror, the key is used only at the gate that fills it.
- Create Secrets Manager secrets c4c/auth-token (a long random token) and, only for the C4C feed, c4c/license-key. Give the task execution role secretsmanager:GetSecretValue on them.
- Download the ECS task definition template, replace <ACCOUNT_ID> and <REGION>, and register it: aws ecs register-task-definition --cli-input-json file://c4c-ecs-task-definition.json. With a mirror, set C4C_UPDATE_URL to it and remove the license-key secret. For Graviton set cpuArchitecture to ARM64.
- Create a service in private subnets. Allow inbound TCP 8080 only from your AI tools or an internal load balancer.
Check: /healthz returns 200 once the first library installs (normally under a minute). Run docker or ECS exec: node server/verify-install.mjs --url http://<host>:8080/mcp for a PASS/FAIL check.
Connect: point Amazon Bedrock AgentCore (Gateway private endpoint or Runtime in your VPC), Claude Code, or any internal MCP client at http://<host>:8080/mcp with header Authorization: Bearer <token>. Cloud assistants that call from the vendor's cloud cannot reach an internal-only server.
Resources: 0.5 vCPU, 1 GiB memory recommended; about 350 MB in /data.
Optional audit log: set C4C_AUDIT_LOG=stdout to record each tool call (arguments, citations returned, library version, and a user identity from your gateway via C4C_AUDIT_USER_HEADER) in your own logs. It is never sent anywhere.
Full guide, connection recipes (Claude Code, Bedrock AgentCore, Microsoft Foundry, Python), security review pack and source: https://github.com/earl-hash/c4c-mcp-server . Support: earl@cfsynergies.com
Resources
Vendor resources
Support
Vendor support
Email earl@cfsynergies.com . Install guide, security overview and source: https://github.com/earl-hash/c4c-mcp-server . Free product; support is best effort, research use only.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.