RegAffairs AI gives Claude cited answers to regulatory and compliance questions, drawn from more than 1,400 datasets published by regulators in 49 jurisdictions, including the EU, UK, US, Canada, Brazil, Mexico, India, Turkey, Japan and Australia. Sources include ECHA, EFSA, the European Commission, FDA, EPA, EMA, HSE, Health Canada, ANVISA, CDSCO and FSSAI. Ask what a regulation requires, whether a substance or ingredient is allowed, what a limit is, what a registration needs, or what changed, and every claim links to the official document it came from. What it covers: - Chemicals: REACH (SVHC Candidate List, Annex XIV and XVII), CLP harmonised classification, UK REACH, US TSCA, California Prop 65, Turkey KKDIK. - Food: EU and US additives, novel foods, food contact, contaminants, labelling, allergen and health claim rules. - Pharma: EU GMP (EudraLex Volume 4), 21 CFR 210/211, ICH guidelines, EMA, FDA and Health Canada drug data. - Medical devices: EU MDR and IVDR, FDA classification and PMA, notified bodies, CDSCO device lists. - Cosmetics: EU Regulation 1223/2009 Annexes II to VI, plus UK, US, Canadian and ASEAN ingredient lists. - Pesticides: EU approvals and MRLs, US EPA tolerances, Brazil ANVISA data. - Biocides: EU BPR active substances, the Article 95 list, EPA disinfectant lists. - Workplace safety: exposure limits from HSE EH40, TRGS 900, INRS, INSST and OSHA. - Textiles: ZDHC MRSL, OEKO-TEX Standard 100, labelling rules. Every result carries the source's title, date and a link to the stored document. When the data holds no record, the answer says so and names what was searched. Built for regulatory affairs, compliance, product stewardship, SDS authoring and consultancies. Lookup tools are read-only; a full question is saved to your RegAffairs AI history and counts on your plan. RegAffairs AI uses public regulatory data and is not affiliated with any regulator. Answers are research, not legal advice.

MCP readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (4036 ms); slow response -1.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 15 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (4036 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 88% of peers; This listing 87 · peer median 81
Latency: Faster than 5% of peers; This listing 1,255 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-10 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/regaffairs/regaffairs/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/regaffairs/regaffairs/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://regaffairsai.com

Listed at (smithery)

https://regaffairsai.com