RegAffairs AI
REMOTE · MCP.REGAFFAIRSAI.COM
Cited answers on chemical, food, pharma, device, cosmetic and pesticide rules, linked to sources.
Available components
Last scanned (59 minutes ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4705 tokens (~313/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.regaffairsai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=regaffairsai.com | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 26a04d9fe7e252ce13110dc5da26a850 |
| SANs: regaffairsai.com, *.regaffairsai.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.regaffairsai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| regaffairsai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.regaffairsai.com/.well-known/oauth-protected-resource/mcp", scope="regaffairs.read"
Bearer resource_metadata="https://mcp.regaffairsai.com/.well-known/oauth-protected-resource/mcp", scope="regaffairs.read" | Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Protected resource metadata
| Document | https://mcp.regaffairsai.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.regaffairsai.com/mcp |
| Authorisation server | https://regaffairsai.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.regaffairsai.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.regaffairsai.com/mcp | HTTPS enforced | 301 | https://mcp.regaffairsai.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
regaffairs_ask_question Ask a regulatory question (full cited answer) ~351
Answers a regulatory question that needs reasoning across several sources, jurisdictions or industries, or one that no industry tool covers. Examples: "is X restricted and what must my SDS say", "compare EU and GB rules for Y", "who must notify, by when, under which article". The tool runs the RegAffairs AI research agent over more than 1,400 regulator datasets and returns a written answer with numbered citations. Sources include ECHA REACH and CLP lists, EU food, cosmetics, plant protection and biocides law, HSE, US EPA TSCA, FDA 21 CFR, California Prop 65, EudraLex Volume 4 GMP, ICH, EMA and Health Canada. Each citation links to the source document. The tool can take up to a minute. If it is still running, it returns `status: "running"` and an `answer_id` for `regaffairs_get_answer_status`. Each call counts as one question on the user's RegAffairs AI plan and is saved to their history. Not intended for a single fact that an industry tool answers (one substance's list status or classification, an exposure limit, an ingredient's status, an MRL, a drug or device register entry). Not intended for legal advice, clinical trial design or FDA submission strategy.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Optional hint. |
| jurisdictions | array | – | Optional ISO codes to focus on, e.g. ["EU","GB","US","US-CA","TR","CA","BR"]. |
| question | string | yes | The question in the user's words. Include substance names with CAS/EC numbers, the product type and the market when known. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer_id | – | yes | – |
| answer_markdown | – | – | – |
| answer_url | – | – | – |
| datasets_searched | array | yes | – |
| message | string | – | – |
| sources | array | yes | – |
| status | string | yes | – |
| truncated | boolean | – | – |
| web_sources_used | boolean | yes | – |
No examples provided.
regaffairs_check_biocide_active_substance Check a biocide active substance, product type or disinfectant registration ~382
Checks whether a biocidal active substance is approved and for which product types (PT1 to PT22), whether a supplier is on the Article 95 list, whether a biocidal product or disinfectant is authorised, and which EPA-registered disinfectants work against a pathogen. EU coverage: BPR active substance approvals, the Article 95 supplier list, Union authorised biocidal products, BPC opinions and the product type definitions. National: the GB biocides active substances, GB Article 95 list and GB biocidal products register (HSE), the French SIMMBAD inventory and the ANSES biocide decisions register, and the German BAuA register of notified biocidal products. US: EPA List N and the other selected EPA-registered disinfectant lists by pathogen. Canada: Health Canada's archived COVID-19 lists of hard-surface disinfectants and hand sanitizers. Give an active substance or a product name. Not intended for plant protection products or MRLs (`regaffairs_check_pesticide_approval_and_mrl` covers those).
| Name | Type | Req | Description |
|---|---|---|---|
| active_substance | string | – | Active substance name or CAS, e.g. 'permethrin', 'hydrogen peroxide'. Give active_substance or product_name. |
| include_suppliers | boolean | – | Add Article 95 supplier entries. |
| jurisdictions | array | – | – |
| product_name | string | – | Biocidal product or disinfectant name, or an EPA registration number. Give active_substance or product_name. |
| product_type | string | – | e.g. 'PT18' (insecticides), 'PT8' (wood preservatives). |
| target_pathogen | string | – | For US disinfectant lists, e.g. 'SARS-CoV-2', 'norovirus', 'C. difficile'. |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_check_chemical_substance Check a chemical substance: REACH, SVHC, TSCA, Prop 65 status ~381
Checks whether one or more chemical substances (name, CAS or EC number) are registered, listed, restricted or banned, and screens a bill of materials. It resolves the identity against the ECHA C&L Inventory and REACH registered substances, the EU customs inventory (ECICS), the US TSCA Inventory, the Australian AICIS inventory and the Turkish chemical inventory. It then checks the ECHA SVHC Candidate List, REACH Annex XIV (authorisation, with sunset dates), REACH Annex XVII (restrictions, with entry conditions), CoRAP and POPs; the UK REACH candidate, authorisation and restriction lists (HSE) and the UK REACH candidate list policy paper (Defra); Turkey KKDIK Annex 17; US EPA TSCA section 6 risk management rules, SNURs and PFAS reporting; the California Prop 65 list with safe harbor levels; Belgian PFAS restrictions; and the AICIS banned and restricted chemicals list. Accepts up to 50 substances. A substance missing from a list is reported as not listed on it. Not intended for hazard classification, pictograms or UN numbers (`regaffairs_get_ghs_hazard_classification` covers those), exposure limits (`regaffairs_get_workplace_exposure_limits`), or cosmetic, food, pesticide or biocide ingredient status (the matching industry tools cover those).
| Name | Type | Req | Description |
|---|---|---|---|
| identity_only | boolean | – | Only resolve name, CAS and EC (for ambiguous names, salts, hydrates, group entries). |
| jurisdictions | array | – | Default: all. |
| lists | array | – | Default: all lists for the chosen jurisdictions. |
| substances | array | yes | Names, CAS (e.g. 80-05-7) or EC numbers (e.g. 201-245-8). |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_check_cosmetic_ingredient Check a cosmetic ingredient (banned, restricted, max concentration, INCI) ~270
Checks whether a cosmetic ingredient is banned, restricted or permitted, and gives its INCI name, maximum concentration, product-type conditions and label warnings. It covers the EU Cosmetics Regulation (EC) No 1223/2009 Annexes II to VI with entry numbers, the EU common ingredient names glossary (Decision 2019/701, the last published edition), the UK cosmetics rules and UK ingredient opinions, the SCCS Notes of Guidance, ICCR reports on fragrance allergens and nanomaterials, US prohibited and restricted cosmetic ingredients, 21 CFR Parts 700 to 740, the Health Canada Cosmetic Ingredient Hotlist, the ASEAN Cosmetic Directive annexes and the Japanese cosmetic ingredient labelling names list. Not intended for food, medicines or general chemical restrictions (the food, pharma and chemical tools cover those).
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | – | – |
| for_children_under_3 | boolean | – | – |
| function | string | – | Optional, narrows to the matching annex. |
| ingredient | string | yes | INCI name, common name, CAS or EC. |
| jurisdictions | array | – | – |
| product_type | string | – | Optional, e.g. 'face cream', 'hair dye', 'oral care', 'sunscreen', 'spray', 'eye area'. |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_check_drug_or_device_approval Check a drug or medical device approval, classification or shortage ~285
Checks whether a medicine is authorised in a market, with its approval details and shortage status, or a medical device's classification, registration, approval or notified body. Medicines: the FDA Orange Book (approved drugs, therapeutic equivalence, patents and exclusivity), EMA authorised medicines, EMA orphan designations, the EMA, FDA and MHRA shortage lists, the Health Canada Drug Product Database (DIN) and Notice of Compliance database. Devices: the FDA device classification database (product codes, device class, regulation number), FDA De Novo decisions and PMA approvals, FDA MAUDE adverse event reports, MHRA guidance on registering devices for the GB market, EU NANDO notified bodies under the MDR and IVDR, the CDSCO approved device lists (India) and the Italian national medical devices database. Not intended for GMP or ICH guidance (`regaffairs_find_pharma_gmp_and_ich_guidance` covers that), for MDR or IVDR legal requirements, or for clinical trials.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | – |
| jurisdictions | array | – | Default: all held for the product kind. |
| product | string | yes | Medicine brand or active ingredient, DIN, NDA/ANDA number, device name, FDA product code (e.g. 'DXY'), PMA number or notified body number. |
| product_kind | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_check_food_additive_or_ingredient Check a food additive, colour, novel food or food contact substance ~352
Checks whether a food additive (E-number), colour additive, novel food, vitamin or mineral form, food contact substance or contaminant limit is allowed, and under which conditions, in the EU or US. EU coverage: Regulation (EC) No 1333/2008 Annex II with food categories and maximum levels, the Novel Food Union list (Regulation 2015/2283), contaminant maximum levels (Regulation 2023/915), the food supplements Directive 2002/46/EC and fortified foods Regulation 1925/2006, the plastics food contact Union list (Regulation 10/2011), the German BfR food contact recommendations, and EFSA scientific opinions. US coverage: 21 CFR Parts 170 to 189, FDA GRAS notices, the FDA substances added to food inventory, colour additives in 21 CFR Parts 73 and 74 and the FDA colour additive status list, food contact notifications and indirect additives. Not intended for labelling, allergen or health claim questions (`regaffairs_check_food_label_and_allergens` covers those) or pesticide residues (`regaffairs_check_pesticide_approval_and_mrl`).
| Name | Type | Req | Description |
|---|---|---|---|
| contact_material | string | – | For food contact questions. |
| food_category | string | – | Optional, e.g. 'flavoured drinks', 'confectionery' or EU category 14.1.4. |
| ingredient | string | yes | Name, E-number (e.g. E171), INS number, FD&C name (e.g. Red No. 3) or CAS. |
| jurisdictions | array | – | – |
| regime | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_check_food_label_and_allergens Check food labelling, allergen and health claim rules ~317
Answers what a food label must show (mandatory particulars, nutrition declaration, ingredients list, allergen emphasis, gluten-free, date marking), which allergens must be declared, and whether a nutrition or health claim is authorised. It covers the EU Food Information to Consumers Regulation (EU) No 1169/2011, the EU nutrition and health claims Regulation (EC) No 1924/2006 and its register, the GB health claims register, Regulation (EU) No 609/2013 on food for specific groups, US 21 CFR Parts 100 to 169 (food labeling and standards of identity), the FDA authorised and qualified health claims lists, Food Standards Code Standard 1.2.2 on food identification and the FSANZ register of notified food-health relationships (Australia and New Zealand), and FSSAI labelling amendments (India). Not intended for whether an ingredient or additive is allowed (`regaffairs_check_food_additive_or_ingredient` covers that) or for cosmetic labels (`regaffairs_check_cosmetic_ingredient`).
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | The allergen, claim wording, nutrient or particular, e.g. 'sesame', 'vitamin C contributes to the normal function of the immune system'. |
| food_type | string | – | Optional, e.g. 'prepacked', 'prepacked for direct sale', 'non-prepacked', 'infant formula', 'food supplement'. |
| jurisdictions | array | – | – |
| topic | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_check_pesticide_approval_and_mrl Check pesticide approval status and maximum residue levels (MRLs) ~274
Checks whether a plant protection active substance is approved, banned or under review, and gives the maximum residue level (MRL) or tolerance for a crop. EU coverage: approvals under Regulation (EC) No 1107/2009, candidates for substitution, emergency authorisations, MRLs under Regulation (EC) No 396/2005, and the EU fertilising products Regulation 2019/1009 for biostimulants. GB: the HSE active substance register and GB MRLs. US: EPA tolerances (40 CFR 180), registration review dockets and the EPA pesticide chemical search. Also Health Canada pesticide product data, the Australia New Zealand MRL schedule, Codex pesticide residue limits, and ANVISA monographs and re-evaluations (Brazil). Not intended for disinfectants and other biocides (`regaffairs_check_biocide_active_substance` covers those) or for industrial chemicals.
| Name | Type | Req | Description |
|---|---|---|---|
| active_substance | string | yes | Active substance name or CAS, e.g. 'glyphosate'. |
| crop | string | – | For MRLs or tolerances, e.g. 'wheat', 'peaches', 'table grapes'. |
| include | array | – | – |
| jurisdictions | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_check_textile_restricted_substances Check textile restricted substances and labelling (ZDHC, OEKO-TEX, REACH) ~339
Checks whether a substance is restricted in textiles, clothing, footwear or leather and what limit applies under a brand or certification list, and what a textile fibre, care or flammability label must show. Substance lists: the ZDHC MRSL, OEKO-TEX Standard 100 limit values by product class, the bluesign system substances list, REACH Annex XVII entries that apply to textiles and leather (for example entry 72 on CMR substances in clothing), the EU Ecolabel textile criteria, and Japanese household goods limits (formaldehyde). Labelling: the EU textile fibre names Regulation (EU) No 1007/2011, the US Textile Fiber Products Identification Act (16 CFR 303), the FTC care labeling rule (16 CFR 423) and wool and fur rules, the Canadian Textile Labelling Act, and US flammability standards (16 CFR 1610, 1611, 1615, 1616). Give substances or a topic. Not intended for general chemical status outside textiles (`regaffairs_check_chemical_substance` covers that).
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdictions | array | – | – |
| lists | array | – | Default: all. |
| product_class | string | – | OEKO-TEX product class I to IV. |
| substances | array | – | Names, CAS numbers or substance groups, e.g. 'APEOs', 'PFAS', 'azo dyes', '117-81-7'. Give substances or topic. |
| topic | string | – | What to check. Give substances or topic; substances without a topic are checked as restricted_substances. |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_find_pharma_gmp_and_ich_guidance Find pharma GMP and ICH guidance (EU GMP, cGMP, ICH, CTD) ~384
Finds what a GMP or ICH guideline requires and the text of a GMP annex or ICH guideline, and checks whether a UK site holds an MHRA manufacturing or wholesale (GMP/GDP) licence. It covers EU GMP (EudraLex Volume 4, Parts I to IV and Annexes 1 to 21), US cGMP for finished pharmaceuticals (21 CFR Parts 210 and 211), the ICH Quality, Safety, Efficacy and Multidisciplinary guidelines and the ICH M4 Common Technical Document, Directive 2001/83/EC, the MHRA GMDP register (GMP and GDP certificates, manufacturer and wholesaler authorisations), MHRA GMP inspection deficiency data, and EDQM OMCL network market surveillance reports. It returns passages with the guideline code, section and version date. Give a topic, a guideline code or a site or company. It does not count as a question. Not intended for whether a medicine is authorised or in shortage (`regaffairs_check_drug_or_device_approval` covers that), for clinical trial conduct or GCP, or for FDA submission strategy.
| Name | Type | Req | Description |
|---|---|---|---|
| guideline | string | – | Code or annex, e.g. 'Annex 1', 'Q9(R1)', 'Q1A(R2)', 'M7', '211.192'. Give query, guideline or site_or_company. |
| query | string | – | The GMP or ICH topic, e.g. 'contamination control strategy', 'stability testing zones', 'nitrosamine risk assessment'. Give query, guideline or site_or_company. |
| site_or_company | string | – | For MHRA licence lookups: company or site name, or licence number. Give query, guideline or site_or_company. |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_get_answer_status Get the status of a running answer ~87
Fetches the result of a `regaffairs_ask_question` call that returned `status: "running"` and an `answer_id`. It waits up to 40 seconds and returns the finished answer with citations, or `running` again. It does not count as a new question. Not intended for starting a new question.
| Name | Type | Req | Description |
|---|---|---|---|
| answer_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| answer_id | – | yes | – |
| answer_markdown | – | – | – |
| answer_url | – | – | – |
| datasets_searched | array | yes | – |
| message | string | – | – |
| sources | array | yes | – |
| status | string | yes | – |
| truncated | boolean | – | – |
| web_sources_used | boolean | yes | – |
No examples provided.
regaffairs_get_ghs_hazard_classification Get GHS/CLP hazard classification, label elements and UN number ~347
Looks up a substance's hazard classification, GHS pictograms, H-statements, signal word or label elements (for example for SDS sections 2 and 3 or a CLP label), and its UN number and transport hazard class (SDS section 14). It returns the EU CLP Annex VI harmonised entry (hazard classes and categories, H-statements, pictograms, signal word, specific concentration limits, M-factors and the ATP that set it) from ECHA's harmonised classification list and Regulation (EC) No 1272/2008. Optionally it adds the self-classifications notified to the ECHA C&L Inventory, the GB mandatory classification list and GB CLP (HSE), pending CLH intentions and RAC opinions, the Korean GHS classification list, and the US DOT Hazardous Materials Table (49 CFR 172.101: UN number, proper shipping name, hazard class, packing group). Not intended for mixtures, which need the user's own calculation, for ADR, IMDG or IATA transport rules, or for whether a substance is restricted (`regaffairs_check_chemical_substance` covers that).
| Name | Type | Req | Description |
|---|---|---|---|
| include_notified | boolean | – | Add the C&L Inventory notified classifications. |
| include_pending | boolean | – | Add open CLH intentions and RAC opinions. |
| include_transport | boolean | – | Add the US DOT 49 CFR 172.101 entry (UN number, class, packing group). |
| jurisdictions | array | – | – |
| substance | string | yes | Name, CAS, EC, CLP index number or UN number (e.g. UN1090). |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| transport | array | – | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_get_workplace_exposure_limits Get workplace exposure limits (OEL, WEL, PEL, AGW, VLEP) ~324
Looks up occupational exposure limits for a substance (OEL, WEL, PEL, AGW, VLEP, MAC, STEL) in one or more countries, for example for SDS section 8, a COSHH assessment or an OSHA compliance check. It covers HSE EH40 and the COSHH Regulations 2002 (GB), TRGS 900 and the GESTIS substance database (Germany), INRS VLEP tables (France), INSST LEP (Spain), the SER database (Netherlands), FOD WASO limits (Belgium), the HSA chemical agents code (Ireland), Arbeidstilsynet limits (Norway), OSHA annotated PELs, Table Z-1 and the OSHA chemical exposure data (US), Safe Work Australia HCIS, the CSGB chemical agents regulation limits (Turkey), the MOEL exposure limits notice (Korea), NOM-010-STPS-2014 (Mexico), SUVA limit values (Switzerland), the Alberta OHS Code (Canada), and the GESTIS international limit values compilation. Not intended for drinking water, ambient air or food limits (`regaffairs_search_regulations` covers those), or for hazard classification (`regaffairs_get_ghs_hazard_classification`).
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | – | Default: all held. INTL = the GESTIS international compilation; CA-AB = Alberta. |
| limit_types | array | – | Default: all. |
| substance | string | yes | Name, CAS or EC number. |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_list_covered_regulations List the regulations and datasets covered ~136
Lists what RegAffairs AI covers ("do you have the EU Cosmetics Regulation?", "which Brazil pesticide registers are in?", "what do you cover for food in the UK?"), and checks before answering that a regulation or register is available. It returns the live catalogue: dataset id, plain name, regulator, jurisdiction, industry, what it contains and when it was last refreshed. Filter by industry, jurisdiction or a text query. It does not count as a question.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | – |
| jurisdictions | array | – | – |
| limit | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| datasets | array | yes | – |
| total | integer | yes | – |
| truncated | boolean | yes | – |
No examples provided.
regaffairs_search_regulations Search regulation text and source documents ~353
Searches the wording of regulations, guidelines and register entries, for questions that need the text rather than a written answer or that fall in an area no industry tool covers, such as REACH or CLP article text, drinking water limits or industrial emissions reporting. It runs a ranked full-text search over every live dataset and returns passages with citations. It does not count as a question. Examples: REACH (`eu_reach_1907_2006`) and CLP (`eu_clp_1272_2008`) articles and annexes, US EPA drinking water MCLs (`us_epa_npdwr_contaminant_mcls`), the EU E-PRTR (`eu_eea_industrial_reporting_eprtr`). Pass `document_id` from an earlier result to read more of one document. Each dataset is searched in its own language: for a register outside the English-speaking world (Brazil, Turkey, Korea, Japan, China, Latin America and most of the EU), put the terms in that language too, for example 'arsênio arroz' for ANVISA's contaminant limits. Give query or document_id. Not intended for questions an industry tool fits; those tools return structured results.
| Name | Type | Req | Description |
|---|---|---|---|
| datasets | array | – | Optional dataset ids to restrict the search (from regaffairs_list_covered_regulations). |
| document_id | string | – | Read passages from one document returned earlier. Give query or document_id. |
| industry | string | – | – |
| jurisdictions | array | – | – |
| limit | integer | – | – |
| query | string | – | What to search for, in the dataset's language when it is not English. Give query or document_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| not_found | array | yes | – |
| results | array | yes | – |
| sources | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
How do I install the RegAffairs AI MCP server?
RegAffairs AI is a hosted endpoint at https://mcp.regaffairsai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.regaffairsai.com
claude mcp add --transport http com-regaffairsai-regaffairs 'https://mcp.regaffairsai.com/mcp'
What is the RegAffairs AI MCP server?
RegAffairs AI is an MCP server listed in the public MCP registry as com.regaffairsai/regaffairs. Cited answers on chemical, food, pharma, device, cosmetic and pesticide rules, linked to sources. This page covers its hosted endpoint (https://mcp.regaffairsai.com/mcp).
Is the RegAffairs AI MCP server safe to use?
RegAffairs AI scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RegAffairs AI MCP server expose?
RegAffairs AI exposes 15 tools: regaffairs_ask_question, regaffairs_get_answer_status, regaffairs_search_regulations, regaffairs_list_covered_regulations, regaffairs_check_chemical_substance, and 10 more. Their descriptions and schemas cost roughly 4,582 tokens of context every time the server is loaded.
Does the RegAffairs AI MCP server require authentication?
Yes. RegAffairs AI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the RegAffairs AI MCP server still maintained?
RegAffairs AI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.