get_regulatory_deadlines — FedReg Tracker MCP Tool Read-only
get_regulatory_deadlines
(get regulatory deadlines) is one of 12 tools on the
FedReg Tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_regulatory_deadlines from your client
- Claude Code FedReg Tracker get_regulatory_deadlines run in your project directory
- Claude Desktop FedReg Tracker get_regulatory_deadlines ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FedReg Tracker get_regulatory_deadlines ~/.cursor/mcp.json
- VS Code FedReg Tracker get_regulatory_deadlines .vscode/mcp.json
- Zed FedReg Tracker get_regulatory_deadlines ~/.config/zed/settings.json
- Windsurf FedReg Tracker get_regulatory_deadlines ~/.codeium/windsurf/mcp_config.json
- Cline FedReg Tracker get_regulatory_deadlines ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FedReg Tracker get_regulatory_deadlines ~/.gemini/settings.json
- Grok FedReg Tracker get_regulatory_deadlines .mcp.json (in your project root)
- ChatGPT FedReg Tracker get_regulatory_deadlines Settings → Connectors → Advanced → Developer mode
- Claude.ai FedReg Tracker get_regulatory_deadlines Settings → Connectors → Add custom connector
- LangChain FedReg Tracker get_regulatory_deadlines pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fedreg https://fedregtracker.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.