FedReg Tracker MCP server
io.github.agentstructure/fedregagentstructurestreamable-httpv1.0.0Scanned
Federal regulatory intelligence from the Federal Register: search rules and notices, track deadlines
12 tools: 1 can delete or cancel things, 4 change things and 7 only read.
- Reads private data · 5
- Reads text others write · 7
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the FedReg Tracker MCP server can do
The FedReg Tracker MCP server is published by the GitHub account agentstructure. It has 12 tools. It can delete or cancel things (1 tool: manage_regulatory_watchlist) and create or change data (4 tools: track_federal_regulations, list_regulatory_alerts, manage_business_profile and rate_regulatory_alert). 7 tools only read.
5 tools read private data (get_regulatory_document, get_regulatory_deadlines, compare_regulatory_documents and 2 more); 7 tools bring in text other people can write (search_federal_regulations, get_regulatory_document, get_regulatory_timeline and 4 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 1Claude Code: deny
manage_regulatory_watchlistManage this account's watchlists.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Manage this account's watchlists. action=list needs nothing else; other actions need watchlist (name or id). update accepts new filters, alert_preferences or new_name.
Annotations the server declares
- title: Manage watchlists
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
list_regulatory_alertsNew alerts for this account's watchlists, highest priority first: new publications, Public Inspection filings (labeled prepublication), deadline extensions, effective-date changes,…1 finding
Why it is in this group
- The name "list_regulatory_alerts" says "list": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "list_regulatory_alerts" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "list_regulatory_alerts" says "list": a word for reading.
Description, as the server wrote it New alerts for this account's watchlists, highest priority first: new publications, Public Inspection filings (labeled prepublication), deadline extensions, effective-date changes, withdrawals, corrections and deadline reminders. Reading marks them delivered unless peek=true. An empty list means nothing new.
Annotations the server declares
- title: List new regulatory alerts
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
manage_business_profileOptional business profile used to suggest relevance: industries, NAICS codes, business size, regions, regulated activities, interests, federal contractor status.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Optional business profile used to suggest relevance: industries, NAICS codes, business size, regions, regulated activities, interests, federal contractor status. Give only what helps monitoring. action=get reads it.
Annotations the server declares
- title: Manage business profile
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
rate_regulatory_alertTell FedReg Tracker how relevant a document was: relevant, not_relevant, high_priority, already_reviewed, more_like_this or stop_tracking (no more alerts for that document).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Tell FedReg Tracker how relevant a document was: relevant, not_relevant, high_priority, already_reviewed, more_like_this or stop_tracking (no more alerts for that document).
Annotations the server declares
- title: Rate an alert
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
track_federal_regulationsSave a persistent watchlist.No findings
Why it is in this group
- The description's first verb is "save": a word for a change.
Description, as the server wrote it Save a persistent watchlist. FedReg Tracker then monitors the Federal Register and Public Inspection on its own schedule and queues alerts and deadline reminders, with no chat open. Example: 'Track new cybersecurity regulations affecting federal contractors' → {name:'cyber-contractors', filters:{keywords:['cybersecurity'], cfr:[{title:48}]}}. Requires an access key.
Annotations the server declares
- title: Create a regulatory watchlist
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 7Show 7 read-only tools
compare_regulatory_documentsCompare two Federal Register documents (or the latest proposed and final rule for a RIN): exact metadata differences plus sentence-level text differences with verbatim excerpts.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "compare_regulatory_documents" says "compare": a word for reading.
What it can reach
- private-dataThe name "compare_regulatory_documents" says "compare" and "document": it reads documents.
- private-dataThe description's first sentence says "compare" and "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Compare two Federal Register documents (or the latest proposed and final rule for a RIN): exact metadata differences plus sentence-level text differences with verbatim excerpts. Text comparison is labeled partial; it is not a legal redline.
Annotations the server declares
- title: Compare regulatory documents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_cfr_changesChanges to codified CFR text from the eCFR (ecfr.gov): which sections got a new version, when (version, amendment and eCFR issue dates), whether eCFR marks it substantive or remove…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_cfr_changes" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Description, as the server wrote it Changes to codified CFR text from the eCFR (ecfr.gov): which sections got a new version, when (version, amendment and eCFR issue dates), whether eCFR marks it substantive or removed, links to the eCFR page and XML for that date, and Federal Register documents that probably made the change. Parts in watchlists are checked daily; any other part is read on first request. Give cfr_title and cfr_part (or a section like 63.2), or a watchlist with CFR filters. Version metadata, not a text diff; the eCFR is not the official legal edition.
Annotations the server declares
- title: Get CFR changes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_regulatory_deadlinesUpcoming comment deadlines or effective dates from the documents' structured fields, filtered by date range, agency, keywords, or one of your watchlists.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_regulatory_deadlines" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
Description, as the server wrote it Upcoming comment deadlines or effective dates from the documents' structured fields, filtered by date range, agency, keywords, or one of your watchlists. Dates are calendar dates as published.
Annotations the server declares
- title: Get regulatory deadlines
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_regulatory_documentFull structured record for one Federal Register document: status, agencies, publication/comment/effective dates, RINs, dockets, CFR parts, official links, linked rulemakings, deadl…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_regulatory_document" says "get": a word for reading.
What it can reach
- private-dataThe name "get_regulatory_document" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
Description, as the server wrote it Full structured record for one Federal Register document: status, agencies, publication/comment/effective dates, RINs, dockets, CFR parts, official links, linked rulemakings, deadline history, any earlier Public Inspection filing, and (when configured) the Regulations.gov docket title, comment period and posted comment count. Also finds documents still on Public Inspection.
Annotations the server declares
- title: Get a Federal Register document
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_regulatory_intelligence_briefA structured, source-linked brief for one document: what happened, agency, status, who may be affected (from your watchlist when given), why it may matter, key dates, a suggested n…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_regulatory_intelligence_brief" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it A structured, source-linked brief for one document: what happened, agency, status, who may be affected (from your watchlist when given), why it may matter, key dates, a suggested next step, sources, confidence and limitations. Built from source fields, not generated guesses.
Annotations the server declares
- title: Get a regulatory brief
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_regulatory_timelineLifecycle of a rulemaking: proposed rule, comment periods, extensions, final rule, effective date, corrections and withdrawals, with observed events and deadline history.Reads text others writeNo findings
Why it is in this group
- The name "get_regulatory_timeline" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
Description, as the server wrote it Lifecycle of a rulemaking: proposed rule, comment periods, extensions, final rule, effective date, corrections and withdrawals, with observed events and deadline history. Give a RIN, a rulemaking_id or a document_number. Links are 'confirmed' (shared RIN) or 'probable' (shared docket); missing stages are never invented.
Annotations the server declares
- title: Get a rulemaking timeline
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
search_federal_regulationsSearch U.S.Reads text others writeNo findings
Why it is in this group
- The name "search_federal_regulations" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search U.S. Federal Register documents (final rules, proposed rules, notices, presidential documents) live from FederalRegister.gov. Filter by keywords, agency, document type, publication/comment/effective dates, CFR title and part, RIN, docket or industry. Every result states its legal status (a proposed rule is never binding) and official links. No account needed.
Annotations the server declares
- title: Search federal regulations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data5
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:01 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://fedregtracker.com/mcp: tools/list returned 12 tools to an anonymous client, including manage_regulatory_watchlist (destructive), track_federal_regulations (write), list_regulatory_alerts (write), manage_business_profile (write), rate_regulatory_alert (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "list_regulatory_alerts" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "list_regulatory_alerts" says "list": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fedreg https://fedregtracker.com/mcpclaude mcp add --transport http fedreg https://fedregtracker.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fedreg__search_federal_regulations",
"mcp__fedreg__get_regulatory_document",
"mcp__fedreg__get_regulatory_timeline",
"mcp__fedreg__get_regulatory_deadlines",
"mcp__fedreg__compare_regulatory_documents",
"mcp__fedreg__get_cfr_changes",
"mcp__fedreg__get_regulatory_intelligence_brief"
],
"ask": [
"mcp__fedreg__track_federal_regulations",
"mcp__fedreg__list_regulatory_alerts",
"mcp__fedreg__manage_business_profile",
"mcp__fedreg__rate_regulatory_alert"
],
"deny": [
"mcp__fedreg__manage_regulatory_watchlist"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fedreg. Review it before you use it.
Capability tags behind 7 rules
- mcp__fedreg__search_federal_regulations untrusted-input
- mcp__fedreg__get_regulatory_document private-data, untrusted-input
- mcp__fedreg__get_regulatory_timeline untrusted-input
- mcp__fedreg__get_regulatory_deadlines private-data, untrusted-input
- mcp__fedreg__compare_regulatory_documents private-data, untrusted-input
- mcp__fedreg__get_cfr_changes private-data, untrusted-input
- mcp__fedreg__get_regulatory_intelligence_brief private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.agentstructure/fedreg/verify?hash=486c6d45fbd95bf34d0e60f4faaf80d969f4b24e9e713197f67604235d96ce31" | jq -e '.changed == false'Pinned hash 486c6d45fbd9, from Nov 16, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.agentstructure/fedreg/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.agentstructure/fedreg)Source: MCP Registry. Synced Oct 21, 2026, 18:22 UTC.
FedReg Tracker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the FedReg Tracker MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the FedReg Tracker MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: manage_regulatory_watchlist.
Can the FedReg Tracker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the FedReg Tracker MCP server have?
- 12 tools: 1 destructive, 4 write, 7 read. manage_regulatory_watchlist, track_federal_regulations, list_regulatory_alerts, manage_business_profile, rate_regulatory_alert, search_federal_regulations, get_regulatory_document, get_regulatory_timeline and 4 more.
Does the FedReg Tracker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the FedReg Tracker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the FedReg Tracker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.