eCFR MCP Server

by n8laymanco.huggingface.n8layman/ecfr-mcp-server

  • Remote endpoint
  • 10 tools
  • MIT

Tools

  • ecfr_mcp_server_ecfr_compare_regulations Compare regulatory text between two dates to identify changes. Use ecfr_get_title_versions to find valid amendment dates first, then pass two of those dates here. Returns: JSON with diff showing added and removed paragraphs.
  • ecfr_mcp_server_ecfr_get_regulation Retrieve regulatory text for a specific section on a given date. IMPORTANT: Call ecfr_get_title_versions first to get a valid date. Provide section whenever possible. Always provide title explicitly for Parts 46 and 50. Returns: JSON with the regulatory text, citation, and source URL.
  • ecfr_mcp_server_ecfr_get_title_structure Get the hierarchical table of contents for a CFR title on a given date. Use to discover valid part and section identifiers before calling ecfr_get_regulation. Start with depth 2 or 3. Depth 4 on broad titles (2, 42, 45) is blocked. Returns: JSON with the hierarchical structure of the title.
  • ecfr_mcp_server_ecfr_get_title_versions Get amendment/version history for a CFR title. CALL THIS FIRST before ecfr_get_regulation or ecfr_compare_regulations. Each returned version has a 'date' field to use in subsequent calls. Returns: JSON with version history including dates for use in other tools.
  • ecfr_mcp_server_ecfr_list_agencies List federal agencies with slugs and CFR references. Returns: JSON with matching agencies and their CFR references.
  • ecfr_mcp_server_ecfr_list_titles List all 50 CFR titles with names and latest amendment dates. Returns: JSON with all CFR titles.
  • ecfr_mcp_server_ecfr_regulatory_index Get metadata and usage guide for the eCFR MCP tools. READ THIS FIRST. Returns Uniform Guidance (2 CFR Part 200) metadata, latest amendment dates, starter citations, grants-relevant agency slugs, and key rules for valid tool calls. Key rules: - Call ecfr_get_title_versions BEFORE ecfr_get_regulation to get a valid date. - Use ecfr_search for topic/concept discovery. - Always provide title= explicitly; part numbers are NOT unique across titles. - Prefer section-level over part-level requests. Tool call workflow: - Topic question: ecfr_search -> ecfr_get_title_versions -> ecfr_get_regulation - Citation lookup: ecfr_get_title_versions -> ecfr_get_regulation - Change history: ecfr_get_title_versions -> ecfr_compare_regulations - Browse structure: ecfr_get_title_structure. Returns: JSON with regulatory index metadata, starter citations, and usage notes.
  • ecfr_mcp_server_ecfr_search Full-text search across the entire Code of Federal Regulations. START HERE for topic or concept questions. Returns sections ranked by relevance. For Uniform Guidance topics, use agency_slugs='office-of-management-and-budget'. Returns: JSON with search results including citations and source URLs.
  • ecfr_mcp_server_fetch_document Read any public web page, PDF or grants.gov opportunity by its URL and return the text. Use it to look up a website the user names, a funding announcement (RFA, NOFO, solicitation), a policy page or a sponsor guide. Use when the user gives a link instead of pasting text. A grants.gov opportunity link returns the opportunity record (dates, ceiling, cost sharing, synopsis, attachment links) from the grants.gov API; fetch the full-announcement PDF it lists in a second call. NSF and other script-rendered pages have no text: ask for the PDF link. Long documents come back in pages: when the result says truncated, call again with offset = next_offset. When replying to a person about a fetched announcement, include the url as a markdown link so they can open the original, and the attachment links when listed. Call this tool by the exact name it is listed under (it carries this server's prefix). Fetch only addresses the user gave, that a tool returned, or that you know exactly (a site's home pa
  • ecfr_mcp_server_grants_gov_search Search federal funding opportunities on grants.gov (RFAs, NOFOs, program solicitations, BAAs). START HERE when the user wants to find a funding announcement. Then pass a hit's link to the fetch_document tool (listed with this server's prefix, e.g. ecfr_mcp_server_fetch_document) for the full record and its attachment PDFs. When replying to a person, list the hits as a numbered markdown list, one line each: the title as a markdown link to the hit's link, then agency, status and close date. The person can click the link to open the announcement on grants.gov. Offer to fetch one for details or to start a budget. Returns: JSON with hit_count, hits (id, number, title, agency, status, open/close dates, link), the agency facet, and next_start when more remain.

As the server's own listing gives them. We never call a tool.