Federal Register proposed/final rules, notices, executive orders, FAR cases. 8 tools.
This Model Context Protocol (MCP) server provides read-only source tools covering federal contracting research topics, including federal Register proposed/final rules, notices, and executive orders, as well as FAR cases. It exposes 8 tools for retrieving relevant regulatory and rulemaking information.
🛠️ Key Features
8 tools for federal regulatory content
Focus on Federal Register proposed/final rules and notices
Includes executive orders
Supports FAR cases
🚀 Use Cases
Researching federal contracting regulations and rulemaking
Looking up proposed vs. final rules in the Federal Register
Reviewing executive orders relevant to procurement contexts
Consulting FAR case information for federal contracting work
⚡ Developer Benefits
MCP server with standardized tool access
Topics align with governance and procurement data needs (e.g., acquisition, federal acquisition, procurement)
Built for developer consumption using open-source tooling references
⚠️ Limitations
Read-only source tools (no write/update operations mentioned)
Limited scope to the listed Federal Register and FAR-related materials
Free, open-source, read-only source tools for federal contracting research: opportunities, awards, company records, labor pricing, travel rates, regulations, and rulemaking.
Free. MIT-licensed, with no subscription and no credits. Directory installs need no account or API key.
Tested. 5,439 collected regression tests, including live-API tests, across 9 servers and 133 tools, with up to ten audit rounds per server against the live government APIs. Published testing records document each bug fixed and the tests added.
Listed, no keys. 4 servers in the Claude directory and 3 in the ChatGPT directory, with all nine planned for both. Directory installs need no user API key.
One of a kind. The only known MCP server for Acquisition.gov FAR Overhaul model text and agency class deviations.
All nine MCPs install and run locally today; the Local column links to each setup guide. Four are also published in the Claude directory and three in ChatGPT, where installs need no user API key or local setup. The rest are coming soon to the directories.
Claude and ChatGPT: Install from the directory listing. No API key and no setup. The MCP runs on Cloudflare at its own 1102tools.com address, such as usaspending.1102tools.com, and your AI app connects to it over the internet. The hosted servers don't store your queries, results, or conversations, and request logging is turned off, so no one at 1102tools sees what you look up. The server code and Cloudflare setup are public in federal-contracting-mcps. Cloudflare still handles connection data such as IP addresses, and Claude or ChatGPT handles your conversation under its own privacy policy.
Local: The MCP runs on your own computer and works with any MCP-compatible app. Requests go straight from your computer to the government source, and nothing passes through 1102tools.com. SAM.gov, BLS OEWS, GSA Per Diem and Regulations.gov need a free API key from the agency. Each setup guide shows how to get one.
After connecting, choose a matching prompt and replace the bracketed details. If a prompt lists multiple MCPs, connect every one it requires. For other sources or compatible MCP clients, use the server setup instructions below.
Server catalog
Choose the sources your work needs. Each server directory contains its own README, code, configuration, tests, and release notes.
Rulemaking dockets, documents, and public comments.
9
217
Personal key recommended; shared fallback; keyless hosted edition coming soon
Install
For the published Claude and ChatGPT listings, use the directory links above. For other sources or MCP clients, open the selected server's README and follow its installation and configuration instructions.
Configure any required API keys outside chat. The server README identifies the exact environment variables and access limits.
Restart or reconnect the client as needed, and confirm the server's tools are visible. Where provided, get_access_status reports local credential readiness; it does not validate the key with the upstream provider.
Choose a prompt, connect every MCP named beneath it, and replace the bracketed details.
A prompt does not install a server. Local command configuration and remote endpoint configuration differ; use the supported setup documented for the selected server. The directory links above identify the published Claude and ChatGPT listings; other servers use their documented setup instructions.
USAspending package naming: its package is usaspending-gov-mcp and its executable is usaspending-mcp. Use the exact configuration in its README; do not substitute a similarly named package.
Use the sources together
Competitors and teaming: combine USAspending award records with SAM.gov entity and exclusion evidence.
Pricing inputs: compare BLS wages, CALC+ ceiling rates, and GSA travel rates while keeping their different pricing bases clear.
Regulations and policy: use eCFR for codified text, Federal Register and Regulations.gov for rulemaking, and Acquisition.gov for FAR Overhaul model text and posted deviations.
Results reflect upstream data and retrieval time. Check dates, completeness, identity matches, and reported limitations. The MCPs provide evidence; they do not make a contracting or procurement-specific applicability decision.
Request pacing and hosted limits
These are default MCP safeguards, measured in upstream requests to the government data source. One tool call can require multiple upstream requests. They are not agency-published quotas or guaranteed response times.
A 0.6-second interval permits approximately 100 request starts per minute, while budget and concurrency slots remain available. Two simultaneous requests means two may be awaiting responses; it does not mean two start every 0.6 seconds. A rolling window counts the immediately preceding five minutes or hour. Failed and cancelled upstream attempts remain counted.
eCFR XML: uncached XML is fetched one request at a time, with three seconds after the previous XML request completes before the next begins. Eligible XML responses are cached for 300 seconds; a cache hit skips that XML download and its pacing wait. The cache holds 128 entries, 32 MiB total, and 2 MiB per entry. Entries can be evicted earlier for capacity. Tools may still require JSON calls, such as resolving the latest date.
Local versus hosted: running the MCP server yourself gives you its local pacing budget. Processes using the same pacing directory and identity share that budget. Connecting any client to a 1102tools hosted endpoint uses the hosted budget, even if the client application runs on your computer.
Limit
Local MCP process / stdio
Hosted endpoint / plugin for the four services above
Upstream budget and concurrency
Shared by local processes using the same pacing directory and identity
Shared by all users of that MCP, regardless of their incoming IPs
Cloudflare entrance limit
Does not apply
120 HTTP requests per 60 seconds, per incoming IP and Cloudflare location
Hosted backend admission
Does not apply
16 processing + 32 FIFO waiting = 48 accepted requests total, shared across this service's users
Hosted total request deadline
Local/client timeouts apply
55 seconds including upload, queue wait and processing; startup and network latency may add time
Shared IPs and shared service capacity are separate limits. People using the same calling IP can share the 120-per-minute entrance counter. With a cloud AI client, that IP may belong to the AI provider rather than your computer. Cloudflare's counter is approximate and location-specific. Different incoming IPs still share the hosted MCP's upstream budget. For example, ten hosted USAspending users share 500 upstream attempts per five minutes, not 500 each. The four services above have separate budgets; USAspending use does not consume eCFR, CALC+ or Federal Register capacity.
Queued requests enter processing in arrival order when a slot opens. Disconnects, cancellations and deadlines free their slots. A full 48-request admission queue returns HTTP 429 with Retry-After: 5; requests exceeding the deadline return HTTP 504 if no response has started. The upstream limits above remain unchanged, so 16 processing slots do not mean 16 simultaneous agency API calls.
HTTP requests include connection setup, tool discovery and tool calls. They are not equivalent to upstream data requests. Government providers can apply additional limits, including to a shared outbound IP or API key. The 500-per-hour CALC+ policy supports short batches at 0.6-second starts; it does not permit continuous 500-per-five-minute use.
For all nine servers' exact defaults, retry intervals, cache rules, shared-IP behavior and budget persistence, see the complete pacing reference. Acquisition.gov's hosted entrance limit remains 60 HTTP requests per minute. The other servers retain their documented three- or four-second completion delays. Cloudflare rate-limit behavior.
Current source-specific evidence is in each server's testing.md or TESTING.md, with changes in its changelog. Packages version independently. The shared request-pacing code reduces bursts and handles provider errors; it does not create additional provider quota.
This September 2026 documentation refresh changes the public entry points and removes retired setup links. It does not change MCP runtime behavior or claim a new live test of the entire suite. Earlier release narrative is preserved in historical documentation.
License and author
MIT licensed. Built by James Jenrette. Independently developed and not affiliated with or endorsed by any federal agency.