Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Federal Register

REMOTE · FEDERAL-REGISTER.1102TOOLS.COM · 2 COMPONENTS

Federal Register proposed and final rules, notices, executive orders, and FAR cases. 8 tools.

+3 this week 68 Trust /100

Last scanned (7 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3011 tokens (~376/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 0
    • Server version: 1.0.20 → 1.0.21 functional
    • Server version: 1.0.19 → 1.0.20 functional
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 0
    • Tool “get_documents_batch” rewrote its description, which is the text the model reads security
    • Tool “search_documents” rewrote its description, which is the text the model reads security
    • Server version: 1.0.18 → 1.0.19 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://federal-register.1102tools.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=1102tools.com CN=WE1,O=Google Trust Services,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA256 95aa9c629e4e46960e613b0bccefe0cd
SANs: 1102tools.com, federal-register.1102tools.com, *.federal-register.1102tools.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of federal-register.1102tools.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
1102tools.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://federal-register.1102tools.com/mcp Verified 200
http (plaintext) http://federal-register.1102tools.com/mcp Inconclusive 405
MCP tools · 8 exposed · ~3,011 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
far_case_history ~368

Get all Federal Register documents for a FAR/DFARS case or FAC. Pass a docket ID like 'FAR Case 2023-008' (or a FAC number like 'FAC 2025-06'). Runs BOTH a docket-id search and a quoted full-text search, then merges the two result sets (deduped by document number) in chronological order to show the full rulemaking progression: ANPRM -> proposed rule -> final rule -> corrections. The dual query matters: FAC introduction and companion documents often carry only internal docket numbers, so a docket-only search returns a partial set. Docket matching is token-based, not substring: 'FAR Case 2023' matches all 2023 cases (token '2023' matches '2023-008'), but a partial token like 'FAR Case 20' matches nothing. Be specific to avoid false positives. Each document carries matched_by: 'docket' or 'docket+text' when its docket ids name the case, 'text' when it only mentions the case in its text (regulatory agendas, related or companion cases, FAC introductions, public meetings). Read 'text' matches with care. Each underlying search returns at most 100 documents. truncated=True flags that one of the searches hit that cap (docket_matches and term_matches carry the API's full counts); narrow the docket_id if so. Minimum docket_id length is 3 characters to prevent token matches that return unrelated documents (e.g. 'x' matched 65 random dockets in 0.1.x).

NameTypeReqDescription
docket_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_document ~114

Get full details for a single Federal Register document by number. Returns all available fields including full text URLs, docket info, RIN details, page views, topics, corrections, and CFR references. Document numbers look like '2026-03065' (modern), 'E9-12940' or 'X94-70302' (legacy pre-2011 archive), or 'C1-2026-01234' (corrections).

NameTypeReqDescription
document_numberstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_documents_batch ~108

Fetch multiple documents in one call (up to ~20). Pass a list of document numbers to fetch up to about 20 in one call. Always returns {count, results, [errors]}; errors.not_found lists any requested numbers the API could not locate. Results come back in the order requested. Image metadata (images, images_metadata) is left out to keep batches small; get_document returns it.

NameTypeReqDescription
document_numbersarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_facet_counts ~349

Get document counts grouped by type, agency, topic, or time period. Accepts the same filter conditions as search_documents. Returns aggregated counts without individual document results. Facets: type, agency, topic (categorical) plus daily, weekly, monthly, quarterly, yearly (publication-date buckets, useful for trend lines). Useful for understanding the volume of rulemaking by agency, type, or over time within a date range before drilling into specific documents. presidential_document_type (executive_order, proclamation, memorandum, determination, notice, presidential_order, other) narrows to one kind of presidential document, e.g. executive orders per month. At least one filter (agencies, doc_types, term, pub_date_gte/lte, or cfr_title) is required. An unfiltered facet query returns the entire all-time aggregate. FAR Council counts: facets cannot express "filed by DoD AND GSA AND NASA", and no single agency slug covers FAR documents (OFPP only from about mid-2025; 'federal-acquisition-regulation-system' holds 2 documents ever). Count FAR rules with search_documents(far_council=True, doc_types=[...], pub_date_gte/lte=...) and read its count.

NameTypeReqDescription
agencies–––
cfr_part–––
cfr_title–––
doc_types–––
facetstringyes–
presidential_document_type–––
pub_date_gte–––
pub_date_lte–––
term–––

Structured output declared, but exposes no named fields.

No examples provided.

get_public_inspection ~270

Get current public inspection documents (pre-publication). Public inspection documents are FR documents filed for publication but not yet published. Updated business days only. The current-PI endpoint does NOT support server-side filtering. This tool fetches all current PI documents and filters client-side by agency and/or keyword in the title. Useful for getting early notice of upcoming regulatory actions. Parameters: - agency_filter: case-insensitive substring match against agency slugs, names, and short names. Sub-agencies are included: PI documents list only the FILING sub-agency, so the filter is also matched against the Federal Register agency list and every agency below a matching one counts ('defense-department' or 'DOD' also returns Army, Navy, Air Force, Corps of Engineers and Defense Logistics Agency filings). filters_applied.includes_sub_agencies says whether that worked. - keyword_filter: substring match against document titles - limit: max documents returned after filtering (default 50, max 500). Unfiltered dumps can exceed 170KB; narrow with filters or raise the cap.

NameTypeReqDescription
agency_filter–––
keyword_filter–––
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

list_agencies ~334

List agencies with their IDs, names, slugs, and parent agencies. Use the 'slug' values with search_documents() and other tools. Common procurement slugs: - defense-department (DoD) - general-services-administration (GSA) - national-aeronautics-and-space-administration (NASA) - defense-acquisition-regulations-system (DARS/DFARS) - federal-procurement-policy-office (OFPP and the CAS Board) - small-business-administration (SBA) - veterans-affairs-department (VA) The FAR has no single slug. FAR rules and notices are filed jointly under DoD, GSA and NASA; OFPP was added only from about mid-2025, so the OFPP slug misses earlier FAR rules. The agency named 'Federal Acquisition Regulation System' (federal-acquisition-regulation-system) holds 2 documents ever; it carries a note in these results. For FAR documents use search_documents(far_council=True) or open_comment_periods(far_council=True). Parameters: - query: optional case-insensitive substring match against name, short_name, and slug. Recommended: narrow results before pulling full detail. - include_detail: if False (default), returns only id/name/short_name/slug/parent_id. If True, returns all fields (description, urls, etc.). The full dump is ~700KB.

NameTypeReqDescription
include_detailboolean––
query–––

Structured output declared, but exposes no named fields.

No examples provided.

open_comment_periods ~440

Find source-reported open comment periods, soonest indexed deadline first. Covers proposed rules, notices, AND final/interim rules that accept comments (dozens of RULE-type documents have open periods at any time). Queries for comment close date >= today, scans up to 500 matching documents oldest-published first (where the soonest deadlines live), sorts by close date, and returns the first `limit`. Source scope: total_open is the API's matching metadata count; scanned is how many this call examined. When total_open exceeds scanned, narrow with agencies/term for complete indexed coverage. A very recently published document with an unusually short comment window can fall outside the scan in that oversubscribed case. complete means the matching indexed records were scanned, not that every currently open opportunity or controlling deadline was verified. The API's comments_close_on metadata can disagree with DATES after an extension or reopening. Even a zero result needs docket/subject search_documents and get_document DATES/linked publication checks before ruling out comments. Default: searches all agencies. Pass agency slugs to narrow scope, e.g. ['defense-acquisition-regulations-system'] for DFARS or ['general-services-administration'] for GSA and GSAR. Parameters: - far_council: True for open FAR proposed rules and FAR information collections (documents filed jointly by DoD, GSA and NASA; there is no single FAR agency slug and the OFPP tag only appears from about mid-2025). Cannot be combined with agencies. - limit: max documents returned after sorting (default 50, max 100). Unfiltered dumps across all agencies can approach 200KB; several broad agencies together (e.g. DoD + GSA) can pass 100KB, so lower limit for those.

NameTypeReqDescription
agencies–––
far_councilboolean––
limitinteger––
term–––

Structured output declared, but exposes no named fields.

No examples provided.

search_documents ~1,028

Search Federal Register documents. Finds proposed rules, final rules, notices, and presidential documents published in the Federal Register since 1994. Key parameters: - agencies: list of agency URL slugs (OR logic). Use list_agencies() to find slugs. Common: 'defense-department', 'general-services-administration', 'small-business-administration', 'defense-acquisition-regulations-system' (DFARS), 'federal-procurement-policy-office' (OFPP and the CAS Board) - far_council: True for FAR rules, proposed rules and notices (the FAR Council's output). There is no single FAR agency slug: FAR documents are filed jointly under DoD, GSA and NASA, OFPP was added only from about mid-2025 (so the OFPP slug misses earlier FAR rules and adds CAS Board documents), and 'federal-acquisition-regulation-system' holds 2 documents ever. far_council=True keeps documents filed by all three of DoD, GSA and NASA; count is exact when far_council.complete is true (narrow by date if not). Cannot be combined with agencies. For FAR clause changes only, cfr_title=48 + cfr_part='1-99' also works. - doc_types: PRORULE (proposed rule), RULE (final rule), NOTICE, PRESDOCU - term: full-text keyword search (strips stop words) - docket_id: docket identifier (token match). 'FAR Case 2023-008' = exact, 'FAR Case 2023' = all 2023 cases; partial tokens like 'FAR Case 20' match nothing - regulation_id_number: RIN (precise match, e.g., '9000-AO56') - pub_date_gte/lte: publication date range (YYYY-MM-DD) - comment_date_gte/lte: comment close date range - effective_date_gte/lte: effective date range - correction: True finds only the Office of the Federal Register's own correction notices (C1- prefix documents). Agency-issued corrections ('Final rule; correction.', 'Correcting amendment.') are ordinary RULE documents and are not flagged: search doc_types=['RULE'] wi…

NameTypeReqDescription
agencies–––
cfr_part–––
cfr_title–––
comment_date_gte–––
comment_date_lte–––
correction–––
doc_types–––
docket_id–––
effective_date_gte–––
effective_date_lte–––
executive_order_number–––
far_councilboolean––
orderstring––
pageinteger––
per_pageinteger––
presidential_document_type–––
pub_date_gte–––
pub_date_lte–––
regulation_id_number–––
significant–––
term–––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Federal Register MCP server?

Federal Register is a hosted endpoint at https://federal-register.1102tools.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · federal-register.1102tools.com

# add to Claude Code
claude mcp add --transport http com-1102tools-federal-register-mcp 'https://federal-register.1102tools.com/mcp'
Common questions

What is the Federal Register MCP server?

Federal Register is an MCP server listed in the public MCP registry as com.1102tools/federal-register-mcp. Federal Register proposed and final rules, notices, executive orders, and FAR cases. 8 tools. This page covers its hosted endpoint (https://federal-register.1102tools.com/mcp).

Is the Federal Register MCP server safe to use?

Federal Register scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Federal Register MCP server expose?

Federal Register exposes 8 tools: search_documents, get_document, get_documents_batch, get_facet_counts, get_public_inspection, and 3 more. Their descriptions and schemas cost roughly 3,011 tokens of context every time the server is loaded.

Does the Federal Register MCP server require authentication?

No. We connected to Federal Register without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Federal Register MCP server still maintained?

Federal Register is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Federal Register MCP server?

VerifyMCP ran 12 checks on Federal Register, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Federal Register: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.