regulatory_fetch_docket_details — DataNexus MCP MCP Tool
regulatory_fetch_docket_details
(regulatory fetch docket details) is one of 55 tools on the
DataNexus MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call regulatory_fetch_docket_details from your client
- Claude Code DataNexus MCP regulatory_fetch_docket_details run in your project directory
- Claude Desktop DataNexus MCP regulatory_fetch_docket_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DataNexus MCP regulatory_fetch_docket_details ~/.cursor/mcp.json
- VS Code DataNexus MCP regulatory_fetch_docket_details .vscode/mcp.json
- Zed DataNexus MCP regulatory_fetch_docket_details ~/.config/zed/settings.json
- Windsurf DataNexus MCP regulatory_fetch_docket_details ~/.codeium/windsurf/mcp_config.json
- Cline DataNexus MCP regulatory_fetch_docket_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DataNexus MCP regulatory_fetch_docket_details ~/.gemini/settings.json
- Grok DataNexus MCP regulatory_fetch_docket_details .mcp.json (in your project root)
- ChatGPT DataNexus MCP regulatory_fetch_docket_details Settings → Connectors → Advanced → Developer mode
- Claude.ai DataNexus MCP regulatory_fetch_docket_details Settings → Connectors → Add custom connector
- LangChain DataNexus MCP regulatory_fetch_docket_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-server https://datanexusmcp.com/mcpOther tools on this server
- report_feedback
- report_mcpize_link
- validate_tool_output
- search_datanexus_tools
- nonprofit_fetch_nonprofit_by_ein
- nonprofit_search_nonprofits_by_name
- nonprofit_fetch_charity_uk
- security_fetch_package_vulnerabilities
- security_fetch_dependency_graph
- security_fetch_cve_detail
- security_audit_sbom_vulnerabilities
- security_fetch_package_licence
- security_fetch_cisa_kev
- security_fetch_cve_epss
- compliance_fetch_npi_provider
- compliance_search_npi_by_name
- compliance_fetch_finra_broker
- compliance_check_sam_exclusion
- domain_fetch_domain_rdap
- domain_fetch_ssl_certificate_chain
- domain_fetch_dns_records
- domain_fetch_domain_history
- domain_fetch_subdomains
- domain_check_email_security
- domain_fetch_reverse_ip
- legal_fetch_patent_by_number
- legal_search_patents_by_keyword
- legal_fetch_patent_citations
- legal_fetch_inventor_portfolio
- govcon_search_contract_awards
- govcon_fetch_vendor_contract_history
- govcon_fetch_open_solicitations
- regulatory_search_open_rulemakings
- regulatory_fetch_federal_register_notices
- security_fetch_package_maintainer_history
- security_fetch_package_risk_brief
- security_detect_typosquatting
- nonprofit_fetch_nonprofit_full_profile
- security_fetch_cve_watch
- security_audit_sbom_continuous
- security_fetch_licence_analysis
- security_audit_licence_compatibility
- security_fetch_cve_risk_summary
- nonprofit_search_nonprofits_by_category
- nonprofit_fetch_nonprofit_financial_trends
- apikeys_generate_api_key
- apikeys_rotate_api_key
- apikeys_revoke_api_key
- security_audit_sbom_license_policy
- security_fetch_cve_watch_status
- frontend_security_detect_typosquatting
- frontend_security_audit_manifest
- frontend_security_audit_ci_pipeline
- frontend_security_fetch_package_risk_brief
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.