Search any drug, condition, or biopharma company and embed a cited FDA & clinical-trials panel — every approval, safety notice, and trial result links straight to fda.gov or clinicaltrials.gov. A working, deployed app at a live *.windsurf.build URL showing real Synorb data the moment you finish answering the questions — not a mockup. You get the React feature, a server-side /api/vitals route that holds your Synorb REST API key+secret (the browser never sees them), a Recharts phase/timeline visualization, a cited results table, honest empty/partial states that respect Synorb coverage.status, and a scheduled Beacon that re-runs on Windsurf's scheduler so the panel keeps catching new FDA approvals and safety communications. Synorb credentials are requested through CREDENTIALS FIRST; if the user chooses self-provision, use https://synorb.com/connect.
A deployed React feature on *.windsurf.build with a server-side /api route. The user types a drug, condition, or company; the panel renders three cited sections — (1) FDA activity (drug approvals, safety communications, recalls/alerts, newsroom) as a chronological timeline; (2) Clinical Trials by phase, shown as a phase-distribution bar chart plus a per-trial results table with sponsor, condition, and NCT link; (3) NIH/HHS policy & funding context cards. Every card, row, and timeline node links to its real fda.gov / clinicaltrials.gov / nih.gov source_url, shows the published date, significance, and the count of structured claims behind it. A 'Watch this' button saves a Synorb Beacon scoped to the searched entity and schedules it on Windsurf's runtime to surface new approvals/safety notices.
Pulling FDA approvals, drug safety communications, and ClinicalTrials.gov phase-1-through-4 results — each pre-extracted into structured claims and pre-linked to its real government source_url — is a multi-week scraping-and-parsing slog that every health SaaS team rebuilds badly. Vitals Panel turns it into a clicked one-shot that deploys a cited, chart-driven, embeddable React feature on live data in minutes. The provenance is the moat: every claim traces to fda.gov / clinicaltrials.gov, so it survives a compliance review, and the verified HHS stream (~348 manifests/30d, 351 in-window) means it is genuinely populated the day it ships.
No setup to learn. Windsurf asks a handful of normal-person questions — each with a smart default, so “you pick” always works — then builds it with live Synorb data flowing in.
Smart default: Alzheimer's disease
Smart default: Both, with FDA activity on top and a trials-by-phase chart below
Smart default: Last 90 days
Smart default: Yes — check daily and highlight anything new
Smart default: Clean clinical white with a calm teal accent
Calm clinical-white surface, teal accent, generous whitespace. Top: an FDA activity timeline (approvals, safety communications, recalls) as dated nodes, each color-coded by type and clickable to fda.gov. Middle: a Recharts horizontal bar chart of completed trials by phase (Early Phase 1 -> Phase 4) with counts. Bottom: a results table — trial title, sponsor, condition, phase badge, claim_count, NCT link. Every element carries a small 'source' chip linking to the real source_url. Feels like a regulatory affairs dashboard a clinician would trust.
Entity-first layout. A header card for the searched drug/condition/company with its tags and a one-line Brief, then two stacked rails: 'Regulatory' (FDA approvals + safety comms as a vertical cited feed) and 'Evidence' (trials grouped by phase as expandable accordions revealing the structured claims and their confidence/evidence labels). Web-search-sourced background (e.g. mechanism of action) appears in a clearly badged 'Web context' strip, visually separated from Synorb-cited cards. Reads like a living dossier.
Alert-forward, darker dashboard. A prominent 'New since you last looked' banner driven by the saved Beacon, a severity-sorted stream of FDA safety communications and recalls at top (significance-weighted), an approvals timeline strip, and a compact trials-phase sparkline. Optimized for teams who care most about catching new safety signals fast; the Beacon-on-scheduler is the centerpiece rather than a footnote.
INFRA-BACKED Windsurf dev codebase (Devin Desktop / Cascade). BUILD-TIME: register Synorb in ~/.codeium/windsurf/mcp_config.json over Streamable HTTP with Authorization: Bearer ${env:SYNORB_MCP_TOKEN}; the agent uses the MCP (synorb-stream-search to find the HHS/FDA/NIH streams for the chosen topic, then synorb-manifests mode=count for a zero-quota density check, then synorb-manifests compact=true target_count=5-10 to inspect real cited examples) so the UI is built on the true data shape. RUNTIME: a server-side /api/vitals route reads SYNORB_API_KEY + SYNORB_SECRET from .env and calls the Synorb REST API; the React feature fetches only /api/vitals so the browser never holds the key; deploy via App Deploys to *.windsurf.build. MCP token (build) and REST key+secret (runtime) are distinct and both server-side. Credentials are requested only at .env creation, linking https://synorb.com/connect. For the watch/monitor feature, configure+save a Synorb Beacon and execute it by beacon_id on Windsurf's scheduler (Synorb does not cron Beacons).
Credential safetySynorb credentials stay server-side or local — never in client/frontend code. You only enter them when the agent asks, with credentials from synorb.com/connect.
Every card, timeline node, and table row deep-links to its real government source_url — FDA approvals/safety/recalls to fda.gov, completed trials to clinicaltrials.gov/study/NCT##### (verified live: e.g. NCT04195945 Phase 2 AML, NCT05318976 Phase 2 early Alzheimer's), NIH/HHS items to nih.gov / grants.nih.gov. URLs are taken verbatim from each Manifest's source/citation block — never invented. Web-search-derived context (mechanism blurbs, drug background) is visibly badged 'Web' and kept separate from Synorb-cited claims, and any topic with no coverage renders an honest empty state per coverage.status rather than a fabricated card.
Yes. The build prompt connects Synorb at build time to learn the real data shape, then wires live Synorb data into the running product. A working, deployed app at a live *.windsurf.build URL showing real Synorb data the moment you finish answering the questions — not a mockup. You get the React feature, a server-side /api/vitals route that holds your Synorb REST API key+secret (the browser never sees them), a Recharts phase/timeline visualization, a cited results table, honest empty/partial states that respect Synorb coverage.status, and a scheduled Beacon that re-runs on Windsurf's scheduler so the panel keeps catching new FDA approvals and safety communications. Synorb credentials are requested through CREDENTIALS FIRST; if the user chooses self-provision, use https://synorb.com/connect.
Only where they are safe. INFRA-BACKED Windsurf dev codebase (Devin Desktop / Cascade). BUILD-TIME: register Synorb in ~/.codeium/windsurf/mcp_config.json over Streamable HTTP with Authorization: Bearer ${env:SYNORB_MCP_TOKEN}; the agent uses the MCP (synorb-stream-search to find the HHS/FDA/NIH streams for the chosen topic, then synorb-manifests mode=count for a zero-quota density check, then synorb-manifests compact=true target_count=5-10 to inspect real cited examples) so the UI is built on the true data shape. RUNTIME: a server-side /api/vitals route reads SYNORB_API_KEY + SYNORB_SECRET from .env and calls the Synorb REST API; the React feature fetches only /api/vitals so the browser never holds the key; deploy via App Deploys to *.windsurf.build. MCP token (build) and REST key+secret (runtime) are distinct and both server-side. Credentials are requested only at .env creation, linking https://synorb.com/connect. For the watch/monitor feature, configure+save a Synorb Beacon and execute it by beacon_id on Windsurf's scheduler (Synorb does not cron Beacons).
Every card, timeline node, and table row deep-links to its real government source_url — FDA approvals/safety/recalls to fda.gov, completed trials to clinicaltrials.gov/study/NCT##### (verified live: e.g. NCT04195945 Phase 2 AML, NCT05318976 Phase 2 early Alzheimer's), NIH/HHS items to nih.gov / grants.nih.gov. URLs are taken verbatim from each Manifest's source/citation block — never invented. Web-search-derived context (mechanism blurbs, drug background) is visibly badged 'Web' and kept separate from Synorb-cited claims, and any topic with no coverage renders an honest empty state per coverage.status rather than a fabricated card.
A real app. Synorb is the cited data core; it also composes the platform's own tools: Devin Desktop / Cascade agent build loop, Synorb MCP registered in ~/.codeium/windsurf/mcp_config.json (Streamable HTTP, Authorization: Bearer ${env:SYNORB_MCP_TOKEN}), App Deploys to *.windsurf.build, Server-side /api route (Next.js / Express) holding SYNORB_API_KEY + SYNORB_SECRET from .env, Recharts (phase-distribution bar chart + FDA/approvals timeline), React feature (browser fetches only /api, never holds the key), Windsurf runtime scheduler (re-runs the saved Beacon by beacon_id), Web search FOR GAPS ONLY (e.g. a drug's mechanism blurb), visibly badged as web vs Synorb-cited.
A few plain-English questions, each with a smart default so you can just say 'you pick': What do you want to look up first when the panel loads? (a drug name, a condition, or a company); Which should the panel lead with — FDA approvals & safety notices, or clinical-trial results by phase?; How far back should it show by default?; Do you want a 'Watch this' button that keeps checking for new FDA approvals and safety communications on a schedule?; What should it look like — clean clinical white, or a darker dashboard style?.
The same Synorb MCP connects to every major coding agent. Pick yours.
Generate credentials, connect Windsurf, and ship something with live, cited intelligence.