MCP App Store
by KeenEthics
Zucca icon

Zucca MCP Server for Claude and ChatGPT

By Zucca

Overview

Zucca is a regulatory research tool. It gives Claude cited answers from Title 21 of the Code of Federal Regulations (21 CFR), the U.S. rules for food labeling, nutrient and health claims, and dietary supplements, and from FDA guidance on how FDA reads and applies those rules. No sign-up or API key is needed. Ask what the regulations require, permit or define, and Claude can search the text, read whole sections in order, and quote the exact rule. Ask how FDA applies a rule, and Claude can search FDA guidance and read a whole guidance document. All tools are read-only. Every passage links to its source on eCFR or fda.gov, so you can check the answer yourself. Regulations: 21 CFR chapter I, subchapters A (General) and B (Food for Human Consumption, including part 190, Dietary Supplements), and chapter II parts 1300 (Definitions) and 1308 (Schedules of controlled substances). Part 1300 says a botanical dietary ingredient that is not anabolic or androgenic is not an anabolic steroid, and part 1308 holds the hemp exclusions. FDA guidance: food labeling, nutrition, claims, dietary supplements, allergens, ingredients and standards of identity. Guidance is FDA's current thinking, not law. Every guidance passage is marked non-binding, and 21 CFR wins wherever the two differ. Every response states what it covers (the CFR parts and edition, or the guidance scope and document count), so Claude never has to guess the scope. Useful for regulatory, quality and product teams checking labeling rules, nutrient content and health claims, serving sizes and definitions, how FDA interprets a rule, and whether a hemp or cannabinoid ingredient, or a supplement with a steroid-like ingredient, is excluded from the controlled substance schedules. It returns regulation and guidance text, not legal advice. Always confirm against the official source before relying on it. Built by Zucca (zucca.ai).

How to connect

  1. Claude: Open the Zucca listing in the Claude connectors directory and choose Connect. Claude listing Zucca exposes 7 tools here.
  2. ChatGPT: Open the Zucca listing in the ChatGPT app directory and choose Connect. ChatGPT listing Zucca exposes 5 tools here.

Tools

regulations_browse

ChatGPT
Browse the table of contents of 21 CFR. With no part it returns every part held and how many sections each has; with a part it returns that part's sections and their headings in document order. Headings only, never regulation text, so this is the cheap way to find which section a topic lives in before reading it with regulations_getSection. Reach for it when a question is about a whole rather than a phrase — how many sections a part has, every section in a subpart, the complete list of something — because regulations_search returns a ranked sample and a sample can never tell you what a complete set contains, so a count taken from it is confidently wrong; browse returns the whole contents in document order, so you count from the text and then read the section that matters with regulations_getSection. Reach for it too when regulations_findText has found nothing and you need to see what is there. Every result carries a coverage field naming the parts and the annual edition the corpus actually holds, and every row carries an eCFR url built against that edition. A part the corpus does not hold comes back as not found, naming the parts that do exist. There is no paging here: a part returns all of its sections in one call.

regulations_findText

ChatGPT
Find passages of 21 CFR whose text or heading contain a phrase, each returned with its citation and an eCFR url so you can quote the regulation exactly. This is a literal substring match and nothing more: it is not ranked, not semantic, and will not find synonyms or reworded phrasing, so a run of this is not a search of the regulations and an empty result is not evidence a rule does not exist. Prefer a distinctive phrase from the regulation itself over a natural-language question, try a shorter phrase before concluding anything, and use regulations_browse to see what is there when a phrase finds nothing. Matching is case-insensitive. Optionally narrow to one part. Results come back in document order, not by relevance, and every result carries a coverage field naming the parts and the annual edition the corpus actually holds, so scope never has to be assumed. Passages are long, so ask for few and page with nextCursor; isPartial says when a further page exists.

regulations_getCitation

ChatGPT
Read one passage of 21 CFR by its exact id, as returned in the id field by regulations_findText or regulations_getSection. The id looks like "21 CFR 101.9(c)(1)" and sometimes carries an occurrence suffix such as "#2", which is part of the id and must be kept. This does not search: an id you have assembled yourself rather than copied will usually come back not found. Use regulations_getSection when you have a section number rather than a passage id. Returns the passage with an eCFR url pointing at the edition the corpus holds, plus a coverage field naming the parts and edition it holds.

regulations_getSection

ChatGPT
Read a section of 21 CFR in document order, so you can follow a rule through its subsections rather than quoting a fragment. Read it whole because exceptions live next to the rules they modify: a paragraph read on its own can say the opposite of what it means in place. So after a regulations_search hit that starts mid-thought, pull its section here to see the subsection it sits in. Give a paragraph rather than a section to narrow the read to that paragraph and everything nested under it: "101.9(c)(1)" returns (c)(1) and its children, not the rest of (c). Use this once regulations_search, regulations_findText or regulations_browse has told you which section matters, or when you already know it. Each passage comes back with its citation and an eCFR url, and the result carries a coverage field naming the parts and annual edition the corpus actually holds. Long sections page: 101.9 alone runs to over two hundred passages, so check isPartial and nextCursor before treating a page as the whole section. A citation that is not a section reference comes back as invalid input; a section or paragraph the corpus does not hold comes back as not found, saying which of the two it was.

guidance_getDocument

Claude

regulations_browse

Claude
Browse the table of contents of 21 CFR. With no part it returns every part held and how many sections each has; with a part it returns that part's sections and their headings in document order. Headings only, never regulation text, so this is the cheap way to find which section a topic lives in before reading it with regulations_getSection. Reach for it when a question is about a whole rather than a phrase — how many sections a part has, every section in a subpart, the complete list of something — because regulations_search returns a ranked sample and a sample can never tell you what a complete set contains, so a count taken from it is confidently wrong; browse returns the whole contents in document order, so you count from the text and then read the section that matters with regulations_getSection. Reach for it too when regulations_findText has found nothing and you need to see what is there. Every result carries a coverage field naming the parts and the annual edition the corpus actually holds, and every row carries an eCFR url built against that edition. A part the corpus does not hold comes back as not found, naming the parts that do exist. There is no paging here: a part returns all of its sections in one call.

regulations_findText

Claude
Find passages of 21 CFR whose text or heading contain a phrase, each returned with its citation and an eCFR url so you can quote the regulation exactly. This is a literal substring match and nothing more: it is not ranked, not semantic, and will not find synonyms or reworded phrasing, so a run of this is not a search of the regulations and an empty result is not evidence a rule does not exist. Prefer a distinctive phrase from the regulation itself over a natural-language question, try a shorter phrase before concluding anything, and use regulations_browse to see what is there when a phrase finds nothing. Matching is case-insensitive. Optionally narrow to one part. Results come back in document order, not by relevance, and every result carries a coverage field naming the parts and the annual edition the corpus actually holds, so scope never has to be assumed. Passages are long, so ask for few and page with nextCursor; isPartial says when a further page exists.

regulations_getCitation

Claude
Read one passage of 21 CFR by its exact id, as returned in the id field by regulations_findText or regulations_getSection. The id looks like "21 CFR 101.9(c)(1)" and sometimes carries an occurrence suffix such as "#2", which is part of the id and must be kept. This does not search: an id you have assembled yourself rather than copied will usually come back not found. Use regulations_getSection when you have a section number rather than a passage id. Returns the passage with an eCFR url pointing at the edition the corpus holds, plus a coverage field naming the parts and edition it holds.

regulations_getSection

Claude
Read a section of 21 CFR in document order, so you can follow a rule through its subsections rather than quoting a fragment. Read it whole because exceptions live next to the rules they modify: a paragraph read on its own can say the opposite of what it means in place. So after a regulations_search hit that starts mid-thought, pull its section here to see the subsection it sits in. Give a paragraph rather than a section to narrow the read to that paragraph and everything nested under it: "101.9(c)(1)" returns (c)(1) and its children, not the rest of (c). Use this once regulations_search, regulations_findText or regulations_browse has told you which section matters, or when you already know it. Each passage comes back with its citation and an eCFR url, and the result carries a coverage field naming the parts and annual edition the corpus actually holds. Long sections page: 101.9 alone runs to over two hundred passages, so check isPartial and nextCursor before treating a page as the whole section. A citation that is not a section reference comes back as invalid input; a section or paragraph the corpus does not hold comes back as not found, saying which of the two it was.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/zucca"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/zucca)