{"data":{"name":"io.github.cyanheads/openfda-mcp-server","title":null,"description":"Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP.","version":"0.8.1","websiteUrl":null,"repositoryUrl":"https://github.com/cyanheads/openfda-mcp-server","remotes":[{"url":"https://openfda.caseyjhand.com/mcp","type":"streamable-http"}],"packages":[{"version":"0.8.1","identifier":"@cyanheads/openfda-mcp-server","runtimeHint":"stdio","registryType":"npm","runtimeArguments":null,"environmentVariables":null},{"version":"0.8.1","identifier":"@cyanheads/openfda-mcp-server","runtimeHint":"streamable-http","registryType":"npm","runtimeArguments":null,"environmentVariables":null}],"status":"active","isLatest":true,"publishedAt":"2026-10-13T00:38:49.830Z","updatedAt":"2026-10-13T00:38:49.830Z","source":"official-registry","verification":"official","confidence":100,"stars":null,"sources":[{"stars":null,"title":null,"source":"official-registry","sourceId":"io.github.cyanheads/openfda-mcp-server","updatedAt":"2026-10-13T00:38:49.830Z","confidence":100,"websiteUrl":null,"description":"Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP.","verification":"official","repositoryUrl":"https://github.com/cyanheads/openfda-mcp-server"}],"toolIndex":{"tools":[{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_count_values","title":"Openfda Count Values","description":"Aggregate and tally unique values for any field across any openFDA endpoint. Returns ranked term-count pairs sorted by count descending; a date field tallies one term per distinct YYYYMMDD date, ranked the same way. Pair with openfda_search_adverse_events, openfda_search_drug_approvals, openfda_search_device_clearances, openfda_search_recalls, openfda_get_drug_label, or openfda_lookup_ndc when sample records help interpret the aggregates.","inputSchema":{"type":"object","properties":{"endpoint":{"type":"string","enum":["drug/event","drug/label","drug/enforcement","drug/ndc","drug/drugsfda","drug/shortages","food/event","food/enforcement","device/event","device/510k","device/pma","device/recall","device/enforcement","device/classification","device/registrationlisting","device/udi","device/covid19serology","animalandveterinary/event","tobacco/problem","other/substance"],"description":"Full openFDA endpoint path (e.g. \"drug/event\", \"device/classification\")"},"count":{"type":"string","minLength":1,"pattern":"\\S","description":"Field to count. openfda_describe_fields gives the verified expression per field as countAs (null = not countable in any form). Otherwise: append .exact for whole-phrase counting of free-text fields (e.g. \"patient.reaction.reactionmeddrapt.exact\"); count identifier fields openFDA already indexes as keywords (product_ndc, application_number, pma_number) bare — .exact on those is rejected as not countable. A date field (receivedate, report_date, decision_date) is counted bare and yields one term per distinct YYYYMMDD date."},"search":{"description":"Filter query to scope the count (e.g. patient.drug.medicinalproduct:\"metformin\"). Omit to count across every record in the endpoint. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.","type":"string","minLength":1,"pattern":"\\S"},"limit":{"default":100,"type":"integer","minimum":1,"description":"Number of top terms to return. truncated reports whether more distinct terms exist beyond it, except at 1000 — openFDA's own count maximum — where openFDA offers no way to tell. A date field is the exception: openFDA sends every date, so the tool ranks them all and truncated is exact at any limit; scope search to at most limit dates to list each one. Default 100; a larger value returns at most 1000 and says so."}},"required":["endpoint","count"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"59fead289863f97b04d226a8a3e3f1192ee7ac42921fb36c31d5b9a4af0ed148","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_dataframe_describe","title":"Openfda Dataframe Describe","description":"List the tables and column schemas on a DataCanvas staged by an openFDA search tool. Call before openfda_dataframe_query to discover the exact table name, column names, and DuckDB types needed for valid SQL. row_count is the full staged result set, not the inline preview count. Columns typed JSON hold nested openFDA objects/arrays — query them with DuckDB json functions.","inputSchema":{"type":"object","properties":{"canvas_id":{"type":"string","pattern":"^[A-Za-z0-9_-]{10}$","description":"Canvas ID from the canvas_id field of an openFDA search tool response (openfda_search_* or openfda_lookup_ndc), present when the search ran with stage=true."}},"required":["canvas_id"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false},"definitionHash":"a1f696695520cfa2df5ea167a35bddbbd2e88085caaf13b1539d16ba91ae6179","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_dataframe_query","title":"Openfda Dataframe Query","description":"Run a read-only SQL SELECT against a DataCanvas table staged by an openFDA search tool (call one with stage=true; its response carries canvas_id + canvas_table). Enables GROUP BY, COUNT/SUM/AVG, time-series, and joins across the staged result set without re-paging the API. Call openfda_dataframe_describe first to get the exact table and column names. Results are capped at the canvas row limit — when truncated is true, page the rest with ORDER BY plus LIMIT/OFFSET. Scalar fields are stored as text (CAST for numeric math); nested objects/arrays are JSON columns — read them with DuckDB json functions, e.g. json_extract_string(openfda, '$.brand_name[0]'). Only SELECT is allowed — DDL, DML, COPY, and file-reading functions are blocked.","inputSchema":{"type":"object","properties":{"canvas_id":{"type":"string","pattern":"^[A-Za-z0-9_-]{10}$","description":"Canvas ID from the canvas_id field of an openFDA search tool response (openfda_search_* or openfda_lookup_ndc), present when the search ran with stage=true."},"query":{"type":"string","minLength":1,"pattern":"\\S","description":"SQL SELECT against the staged table. Use the table name from openfda_dataframe_describe. Example: \"SELECT classification, COUNT(*) AS n FROM spilled_ab12cd34 GROUP BY classification ORDER BY n DESC\"."}},"required":["canvas_id","query"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false},"definitionHash":"d4e223d62a823e1933c0e475754ee0e4ef72592f67ca057c34b5507eb60f6e67","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_describe_fields","title":"Openfda Describe Fields","description":"Return the searchable field paths for an openFDA endpoint, grouped by category with type and description. Use before constructing a search query to find the correct dotted field path — field names differ per endpoint and are not discoverable from the tool schema alone.","inputSchema":{"type":"object","properties":{"endpoint":{"type":"string","enum":["drug/event","drug/label","drug/enforcement","drug/ndc","drug/drugsfda","drug/shortages","food/event","food/enforcement","device/event","device/510k","device/pma","device/recall","device/enforcement","device/classification","device/registrationlisting","device/udi","device/covid19serology","animalandveterinary/event","tobacco/problem","other/substance"],"description":"openFDA endpoint to describe (e.g. \"drug/event\", \"drug/shortages\", \"device/510k\"). Must be one of the cataloged endpoints."}},"required":["endpoint"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"b8eba1abb6778f15b6c7e08998b75ef9018fd7cf5c97b14b45b729d04bfd324d","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_drug_profile","title":"Openfda Drug Profile","description":"Resolve one drug name to its FDA identity, then fan out in parallel across the bounded per-drug openFDA endpoints and merge into one profile: identity, label highlights, adverse-event summary, recall history, Drugs@FDA approval, and shortage status. Identity and label come from an original packager's label when one matches (identity.is_original_packager says when they do not), approval is the drug's own application ranked over its Drugs@FDA matches, and each section names the product it describes. Replaces chaining openfda_get_drug_label, openfda_search_adverse_events, openfda_search_recalls, openfda_search_drug_approvals, and openfda_search_drug_shortages — and reconciles the identifier drift between endpoints that makes that chaining error-prone. Each section is best-effort: a miss returns null rather than failing the call, and a sub-query the 50 s profile deadline cuts is listed in degraded. For deep dives into any one area, use the dedicated tool.","inputSchema":{"type":"object","properties":{"drug":{"type":"string","minLength":1,"pattern":"\\S","description":"Drug name to profile — brand or generic (e.g. \"metformin\", \"Humira\", \"Glucophage\"). Resolved once to an FDA identity. The Drugs@FDA approval is ranked over this name's matches; meta.fanOutKey reports the name the recall and shortage sub-queries searched."}},"required":["drug"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"502c1cb6527ea74bd4154c946155b84d0dca91ae16dd937e66d3f200541f7268","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_get_drug_label","title":"Openfda Get Drug Label","description":"Look up FDA drug labeling (package inserts / SPL documents). Check indications, warnings, dosage, contraindications, active ingredients, or any structured label section. A label runs to tens of thousands of tokens, so a page that exceeds the inline budget returns the list of available sections instead; re-call with sections to pull the ones you need.","inputSchema":{"type":"object","properties":{"search":{"type":"string","minLength":1,"pattern":"\\S","description":"Query targeting label fields. Examples: openfda.brand_name:\"aspirin\", openfda.generic_name:\"metformin\", openfda.manufacturer_name:\"pfizer\". To fetch one product's label, pass set_id with the SPL UUID returned in earlier results; it returns the label's current revision only, since openFDA does not serve earlier ones. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request."},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Example: effective_time:desc. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"default":5,"type":"integer","minimum":1,"description":"Labels per page. Labels are large, and the cost of a sections selection is the section summed across every record on the page — so it scales with this limit. Lower it before widening a selection. Default 5; a larger value returns at most 1000 and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"sections":{"description":"Label sections to return, e.g. [\"boxed_warning\",\"indications_and_usage\"]. Names come from the outline an oversized page returns, or from openfda_describe_fields. Omit for the whole label — which returns the section outline instead when the page exceeds the inline size budget; an empty list is treated as omitted. A selection is returned whole even when it exceeds that budget, with its serialized size reported on the notice; the outline names a section measured to fit at the requested limit. Sections ending in _table hold SPL table markup: raw in structured results, rendered as Markdown tables in the text output. Metadata (openfda, set_id, id, effective_time, version) is returned either way and counts toward the size.","type":"array","items":{"type":"string","minLength":1,"pattern":"\\S","description":"A top-level label section name."}}},"required":["search"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"3b65a453e6b2ce6e71af1b4974a68e8a9300da1519f0029d3d9c5aef94465038","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_lookup_ndc","title":"Openfda Lookup Ndc","description":"Look up drugs in the NDC (National Drug Code) Directory. Identify drug products by NDC code, find active ingredients, packaging details, or manufacturer info. Pair with openfda_get_drug_label using the returned brand_name or set_id to read the package insert. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"search":{"type":"string","minLength":1,"pattern":"\\S","description":"openFDA search query. Examples: product_ndc:\"0363-0218\", brand_name:\"aspirin\", generic_name:\"metformin\", labeler_name:\"walgreen\", active_ingredients.name:\"ASPIRIN\". Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request."},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Example: listing_expiration_date:desc. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"default":25,"type":"integer","minimum":1,"description":"Records per page. A record grows with its packaging list, so a product with many package configurations is several times the size of one with a single package. Default 25; a larger value returns at most 1000 and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"brand_name\", \"active_ingredients.name\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (product_ndc), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or an openFDA search tool (openfda_search_*). Passing one stages this lookup onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"required":["search"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"bc76f759d5a8c1d2133acfeb3852ce5811a2004c9e5940dc31eac5a23b068ae1","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_search_adverse_events","title":"Openfda Search Adverse Events","description":"Search adverse event reports across drugs, food, and devices. Use to investigate safety signals, find reports for a specific product, or explore reactions by demographics. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"category":{"type":"string","enum":["drug","food","device"],"description":"Product category — each has different field schemas in the response"},"search":{"description":"openFDA search query. Examples: patient.drug.medicinalproduct:\"aspirin\", patient.reaction.reactionmeddrapt:\"nausea\" AND serious:\"1\". Omit both search and sort to browse the newest reports first. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.","type":"string","minLength":1,"pattern":"\\S"},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. Sortable date fields are category-specific: drug → receivedate (or receiptdate), food → date_created (or date_started), device → date_received (or date_of_event). A field from another category (e.g. receivedate on food or device) causes a query error — use the field for this category. With search also omitted, the default is newest first: drug receivedate:desc, food date_created:desc, device date_received:desc. A search with no sort keeps openFDA's own order.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"type":"integer","minimum":1,"description":"Records per page. Default and cap by category: drug 5 (cap 25), food 25 (cap 1000), device 10 (cap 175); a larger value returns at most that cap and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"receivedate\", \"patient.drug.medicinalproduct\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (safetyreportid, report_number, mdr_report_key), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or another openFDA search tool (openfda_search_* or openfda_lookup_ndc). Passing one stages this search onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"required":["category"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"8828452159b37d7d6c956720b3d9036a6975ff53150ad9771b86abebfd37bfdb","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_search_animal_events","title":"Openfda Search Animal Events","description":"Search adverse event reports for veterinary drugs and devices submitted to the FDA Center for Veterinary Medicine. Records include animal species, breed, age, weight, drug name and route, adverse reactions (using VeDDRA terminology), and outcome. Use to investigate safety signals for veterinary products, find reports by animal species or drug, or explore reaction patterns. Brand and manufacturer names are masked as \"MSK\" on every record (the FDA null flavor for withheld data), so find a product by active ingredient on drug.active_ingredients.name, unsuffixed. An ingredient search spans every product containing it and cannot attribute reports to one brand; drug.manufacturer.registration_number (the full value, e.g. \"USA-USFDACVM-N141426\") narrows it to one approval. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"search":{"description":"openFDA search query using field:value syntax. Examples: animal.species:\"Dog\", drug.active_ingredients.name:\"Fluralaner\", reaction.veddra_term_name:\"Vomiting\", serious_ae:\"true\". Omit to browse newest first, sorted by original_receive_date:desc. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.","type":"string","minLength":1,"pattern":"\\S"},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Omitted with no search, defaults to original_receive_date:desc, newest first; omitted with a search, results come in openFDA's relevance order. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"default":25,"type":"integer","minimum":1,"description":"Records per page. Default 25; a larger value returns at most 450 and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"original_receive_date\", \"animal.species\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (unique_aer_id_number), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or another openFDA search tool (openfda_search_* or openfda_lookup_ndc). Passing one stages this search onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"74d84cceb9694d6ac14aeff54f199fd3f8b5e5b95ec073c0da58b769c3082686","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_search_device_clearances","title":"Openfda Search Device Clearances","description":"Search FDA device premarket notifications — 510(k) clearances and PMA approvals. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"pathway":{"type":"string","enum":["510k","pma"],"description":"Premarket pathway. 510(k) is the most common; PMA is for higher-risk devices."},"search":{"description":"openFDA search query. Examples: applicant:\"medtronic\", advisory_committee_description:\"cardiovascular\", product_code:\"DXN\", openfda.device_name:\"catheter\". Omit to browse newest first, sorted by decision_date:desc. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.","type":"string","minLength":1,"pattern":"\\S"},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Omitted with no search, defaults to decision_date:desc, newest first; omitted with a search, results come in openFDA's relevance order. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"type":"integer","minimum":1,"description":"Records per page. Default and cap by pathway: 510k 10 (cap 175), pma 25 (cap 575); a larger value returns at most that cap and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"decision_date\", \"applicant\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (k_number, pma_number, supplement_number), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or another openFDA search tool (openfda_search_* or openfda_lookup_ndc). Passing one stages this search onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"required":["pathway"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"2a9b3ba1244a79cbfffb2244af2a847f5423ff55fddf84b2397eee9bdfa70d83","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_search_drug_approvals","title":"Openfda Search Drug Approvals","description":"Search the Drugs@FDA database for drug application approvals (NDAs and ANDAs). Returns application details, sponsor info, and full submission history. Pair with openfda_get_drug_label to read the approved label, or openfda_count_values to aggregate by sponsor_name, product_type, or route. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"search":{"description":"openFDA search query. Examples: products.brand_name:\"eliquis\" (any letter case; openfda.* fields are filled only on harmonized applications, so openfda.brand_name misses the rest), sponsor_name:\"PFIZER\", submissions.submission_type:\"ORIG\" AND submissions.review_priority:\"PRIORITY\". Exact quoted values can be case-sensitive on some fields — sponsor_name is stored uppercase, so use sponsor_name:\"PFIZER\" (a lowercase quoted value returns no matches). Omit to browse by latest submission, newest first, sorted by submissions.submission_status_date:desc. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.","type":"string","minLength":1,"pattern":"\\S"},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Omitted with no search, defaults to submissions.submission_status_date:desc: applications by their latest submission status date, supplements included, newest first — not by approval date. Omitted with a search, results come in openFDA's relevance order. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"default":25,"type":"integer","minimum":1,"description":"Records per page. A record carries its application's whole submission history, so a long-running application is an order of magnitude larger than a recent one. Default 25; a larger value returns at most 375 and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"sponsor_name\", \"submissions.submission_status_date\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (application_number), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or another openFDA search tool (openfda_search_* or openfda_lookup_ndc). Passing one stages this search onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"8af8e26c099430cdeb9013551852c16c7be01656ed8f0673e76ef7a183c50c8a","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_search_drug_shortages","title":"Openfda Search Drug Shortages","description":"Search FDA drug shortage records. Returns per-product shortage status, availability, therapeutic category, dosage form, manufacturer, and dates. Use to check whether a drug is currently in shortage, find all oncology drugs with supply issues, or retrieve the openfda block (brand_name, product_ndc, rxcui) to chain into openfda_get_drug_label or openfda_lookup_ndc. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"search":{"description":"openFDA search query using field:value syntax. Examples: status:\"Current\", therapeutic_category:\"Oncology\", generic_name:\"carboplatin\", company_name:\"pfizer\". Omit to browse all records. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request. Call openfda_describe_fields({ endpoint: \"drug/shortages\" }) for the complete field list.","type":"string","minLength":1,"pattern":"\\S"},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Example: update_date:desc. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"default":25,"type":"integer","minimum":1,"description":"Records per page. Default 25; a larger value returns at most 1000 and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"generic_name\", \"status\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (package_ndc), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or another openFDA search tool (openfda_search_* or openfda_lookup_ndc). Passing one stages this search onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"d226b41957d3a930bb3d323f5adfd7ace21ad4d2c6145b0101f4aae8979ffe35","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_search_recalls","title":"Openfda Search Recalls","description":"Search enforcement reports and recall actions across drugs, food, and devices. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"category":{"type":"string","enum":["drug","food","device"],"description":"Product category"},"endpoint":{"default":"enforcement","description":"Report type. Default enforcement. The recall endpoint is only available for devices.","type":"string","enum":["enforcement","recall"]},"search":{"description":"openFDA search query. Examples: classification:\"Class I\" (also \"Class II\" or \"Class III\"), recalling_firm:\"pfizer\", reason_for_recall:\"undeclared allergen\". Omit to browse newest first, sorted by report_date:desc (event_date_initiated:desc on the device recall endpoint). Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.","type":"string","minLength":1,"pattern":"\\S"},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort (e.g. report_date:desc,status.exact:asc). Omitted with no search, defaults to report_date:desc (event_date_initiated:desc on the device recall endpoint), newest first; omitted with a search, results come in openFDA's relevance order. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"type":"integer","minimum":1,"description":"Records per page. Default and cap by category and endpoint: drug or food enforcement 25 (cap 1000), device enforcement 10 (cap 125), device recall 10 (cap 50); a larger value returns at most that cap and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"recalling_firm\", \"reason_for_recall\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (recall_number, product_res_number), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or another openFDA search tool (openfda_search_* or openfda_lookup_ndc). Passing one stages this search onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"required":["category"],"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"6b656067d8f8ccb0f4f316cb7a3c15856ae0adc92a5e212f25018ba360ce6119","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"},{"serverName":"io.github.cyanheads/openfda-mcp-server","endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","name":"openfda_search_tobacco_reports","title":"Openfda Search Tobacco Reports","description":"Search problem reports submitted to the FDA for tobacco products, including e-cigarettes, vaping products, cigarettes, and smokeless tobacco. Reports capture product type, reported health problems (e.g. seizure, chest pain), product problems (e.g. exploding battery), whether a non-user was affected, and submission date. Use to investigate safety signals, find reports by product type, or analyze health effects. With stage=true, call openfda_dataframe_describe for the staged columns, then openfda_dataframe_query for SQL.","inputSchema":{"type":"object","properties":{"search":{"description":"openFDA search query using field:value syntax. Examples: tobacco_products:\"Electronic cigarette\", reported_health_problems:\"Seizure\", nonuser_affected:\"Yes\". Omit to browse newest first, sorted by date_submitted:desc. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.","type":"string","minLength":1,"pattern":"\\S"},"sort":{"description":"Sort expression — a field path optionally suffixed with :asc or :desc (any letter case; :ascending and :descending are also accepted, and every direction is sent as asc or desc); comma-separate for multi-field sort. Omitted with no search, defaults to date_submitted:desc, newest first; omitted with a search, results come in openFDA's relevance order. Field paths take only letters, digits, underscores, and dots; any other character or direction is rejected before the request. A well-formed but non-sortable field still causes a query error — use a documented field name.","type":"string","minLength":1,"pattern":"^\\s*(?=\\S)(?![,:.])(?!.*,(?: *[,:.]|\\s*$))(?!.*[^\\s,] +[^\\s,])(?!.*\\.(?:[.:,\\s]|$))(?!.*:(?!(?:[Aa][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?|[Dd][Ee][Ss][Cc](?:[Ee][Nn][Dd][Ii][Nn][Gg])?)(?: *,|\\s*$)))[A-Za-z0-9_.:, ]*[A-Za-z0-9_]\\s*$"},"limit":{"default":25,"type":"integer","minimum":1,"description":"Records per page. Default 25; a larger value returns at most 1000 and says so."},"skip":{"default":0,"type":"number","minimum":0,"description":"Number of records to skip for pagination (default 0). openFDA caps pagination at 25000 records; a higher value returns a pagination_limit_reached error."},"fields":{"description":"Dotted record paths to keep on each returned record, e.g. [\"date_submitted\", \"reported_health_problems\"] — any key path on a returned record works, and openfda_describe_fields lists the searchable ones. Each record is projected to these paths plus its identity key (report_id), identically on both response surfaces, and a path through an array applies to every element. Use it when records are large: when a record on the page serializes above 24000 bytes, page_bytes reports the page's size and page_largest_fields names the largest record's biggest fields. A path no returned record carries is named on the notice. Omit for whole records. Paths take only letters, digits, underscores, and dots; anything else is rejected before the request. With stage=true, only the inline page is projected — the staged table keeps its columns.","type":"array","items":{"type":"string","pattern":"^(?!\\.)(?!.*\\.\\.)(?!.*\\.$)[A-Za-z0-9_.]+$"}},"stage":{"default":false,"description":"Stage the matched set on a DataCanvas for SQL analysis — openfda_dataframe_describe lists the staged columns, openfda_dataframe_query runs the SQL. Default false — the call returns one page for one upstream request. When true, records are also drained onto a canvas table up to a size budget (staged_rows reports how many reached it). Staging is for record-level SQL over a bounded slice; for a distribution over everything that matched, openfda_count_values aggregates server-side in one request. Requires CANVAS_PROVIDER_TYPE=duckdb.","type":"boolean"},"canvas_id":{"description":"Canvas ID returned by a prior stage=true call to this tool or another openFDA search tool (openfda_search_* or openfda_lookup_ndc). Passing one stages this search onto that canvas (same effect as stage=true) so result sets accumulate for cross-table joins. Omit to stage onto a fresh canvas.","type":"string","pattern":"^[A-Za-z0-9_-]{10}$"}},"$schema":"https://json-schema.org/draft/2020-12/schema","additionalProperties":false},"annotations":{"readOnlyHint":true},"definitionHash":"1bcee837929bb84e8b758140c6379075261e9ea17184dcce1f4c1b30cc427008","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-19T08:46:05.465Z","metadataTrust":"untrusted"}],"endpoints":[{"endpointFingerprint":"48cadf5fb280c04ce4348f00c3151e3153c0ea4a50cd3fae0c169caad9f7c500","protocol":"streamable-http","status":"indexed","toolCount":14,"observedAt":"2026-11-19T08:46:05.465Z"}],"authentication":"unknown"},"connectionConfigurations":{"status":"ready","authentication":"not embedded","clients":{"Claude Desktop":{"mcpServers":{"io.github.cyanheads/openfda-mcp-server":{"url":"https://openfda.caseyjhand.com/mcp"}}},"Cursor":{"mcpServers":{"io.github.cyanheads/openfda-mcp-server":{"url":"https://openfda.caseyjhand.com/mcp"}}},"VS Code":{"servers":{"io.github.cyanheads/openfda-mcp-server":{"type":"http","url":"https://openfda.caseyjhand.com/mcp"}}}}},"resourceType":"mcp-server","callable":true,"runtime":{"callable":true,"protocols":["mcp"]},"interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://openfda.caseyjhand.com/mcp"},{"protocol":"mcp","package":"@cyanheads/openfda-mcp-server","registryType":"npm","version":"0.8.1"},{"protocol":"mcp","package":"@cyanheads/openfda-mcp-server","registryType":"npm","version":"0.8.1"}],"profile":{"apiVersion":"1","schemaVersion":"1","id":"mcp-server:io.github.cyanheads%2Fopenfda-mcp-server","resourceType":"mcp-server","canonicalUrl":"https://www.agentsjunction.com/api/v1/servers/io.github.cyanheads%2Fopenfda-mcp-server","name":"io.github.cyanheads/openfda-mcp-server","description":"Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP.","interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://openfda.caseyjhand.com/mcp"},{"protocol":"mcp","package":"@cyanheads/openfda-mcp-server","registryType":"npm","version":"0.8.1"},{"protocol":"mcp","package":"@cyanheads/openfda-mcp-server","registryType":"npm","version":"0.8.1"}],"capabilities":[],"identity":{"source":"official-registry","websiteUrl":null,"repositoryUrl":"https://github.com/cyanheads/openfda-mcp-server","version":"0.8.1"},"verification":{"state":"official","confidence":100},"operations":{"resourceType":"mcp-server","name":"io.github.cyanheads/openfda-mcp-server","status":"online","lastCheckedAt":"2026-11-20T09:18:24.323Z","lastSuccessfulCheck":"2026-11-20T09:18:24.323Z","latencyMs":248,"consecutiveFailures":0,"isStale":false,"checks":{"endpointReachable":true,"protocolValid":true,"agentCardValid":null,"mcpHandshakeValid":true},"lastSeen":null,"lastSuccessfulInteraction":null,"lastHealthCheck":"2026-11-20T09:18:24.323Z","source":{"type":"health-check","url":null},"observedAt":"2026-11-20T09:18:24.323Z"},"security":null,"timestamps":{"createdAt":"2026-10-13T00:38:49.830Z","updatedAt":"2026-10-13T00:38:49.830Z","observedAt":"2026-11-20T09:18:24.323Z"},"compatibility":{"serverVersion":"0.8.1","protocolVersions":[{"protocol":"mcp","version":null}]}}}}