Fulcra Context MCP vs Openfda
A side-by-side look at the Fulcra Context MCP and Openfda MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fulcra Context MCP for biology & bioinformatics work as a local process; choose Openfda for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fulcra Context MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
FULCRA_ENVIRONMENT. - You want tools like
get_workouts, annotations_catalog, create_data_type.
Choose Openfda when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
fda_drug_events, fda_drug_approvals, fda_applications_by_cik.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 63/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | FULCRA_ENVIRONMENT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 25 | 18 |
| Full listing | View Fulcra Context MCP | View Openfda |
Tools & capabilities
Fulcra Context MCP tools 25
get_workoutsGet details about the workouts that the user has done during a period of time. Result timestamps will include time zones. Always translate timestamps to the user's local time zone when this is known.annotations_catalogGet the list of all annotation data types the user has defined. This does not get the actual values the user has recorded; for that, use the `get_records` tool. Use this tool to get the IDs and types to pass to `get_records`.create_data_typeCreate a user-defined data type so the user can track something new. Choose base_type by what gets recorded: "moment" (a point in time), "duration" (a time range), "boolean" (yes/no), "numeric" (a number, optionally with a unit), or "scale" (a 1-5 rating with labels). The new type appears in get_data_catalog, and recorded values are readable with get_records. Creation is reversible with archive_data_type.archive_data_typeArchive (soft-delete) a user-defined data type. The type and its recorded data are recoverable with restore_data_type. Only user-defined types (created via create_data_type or the Context app) can be archived.restore_data_typeRestore an archived user-defined data type.record_dataRecord a single record for a recordable data type. Use get_data_catalog to find data types; user-defined ones use the "<BaseType>/<uuid>" ID form (create new ones with create_data_type). Recorded data can be read back with get_records.get_data_catalogGet all data types available for this user, grouped by relevant MCP tool. Includes health and sensor measurements, location, events, and user-defined annotation types. Call this before requesting time-series data or raw records, and only use a data type with the tools named in its group.get_time_seriesGet calculated per-interval time-series values for a single data type. Only data types that `get_data_catalog` lists as usable with this tool are supported; other types can be read with `get_records`. Result timestamps include time zones; translate them to the user's local time zone when known.get_recordsRetrieve the raw records of any data type during a time period. Works with every type listed by `get_data_catalog`, including user-defined ones ("<BaseType>/<uuid>" IDs); the correct API endpoint is chosen automatically. Records that cover a time range are included when any part of it intersects the requested window. Results are raw samples — they may come from multiple sources and can overlap; for calculated per-interval values of numeric data types, prefer `get_time_series`. Result timestamps include time zones; translate them to the user's local time zone when known.get_data_updatesSummarize the data that arrived in the user's account during a period of time. The time range filters on when records were processed/synced into Fulcra, NOT on the records' own timestamps — e.g. last night's sleep records typically arrive this morning. Use this to find out what new data exists since a previous check, then query the changed types with the appropriate tools.get_sleepReturn the user's sleep data at a chosen level of detail. Pick the coarsest level that answers the question — results grow with detail: - "aggregate": stage totals per period (default 1 day), one row per period per stage. Best for multi-day questions ("how did I sleep this month"). - "cycles": one row per sleep session. - "stages": every stage interval (the full hypnogram); single-night detail. Sleep spans midnight (starts day N, ends day N+1) — extend the time range accordingly. Stage integers: 0=In Bed, 1=Asleep/Unknown, 2=Awake, 3=Light, 4=Deep, 5=REM. Result timestamps include time zones; translate them to the user's local time zone when known.get_location_at_timeGets the user's location at the given time. If no sample is available for the exact time, searches for the closest one up to window_size seconds away. Result timestamps will include time zones. Always translate timestamps to the user's local time zone when this is known.- +13 more on the listing page
Openfda tools 18
fda_drug_eventsSearch FAERS adverse event reports by drug name, MedDRA reaction term, or date range. Returns report counts, reaction types, seriousness levels, and dates. Natural multi-word reaction phrasing is retried against MedDRA preferred-term word order before an empty result is reported. FAERS reports do not establish incidence or causality.fda_drug_approvalsFind FDA-approved drugs by brand name, active ingredient, or application number. To find generic versions of a drug, search by active ingredient using products.active_ingredients.name (NOT openfda.generic_name — that field only works in the label endpoint). IMPORTANT: drug names in the FDA database are stored in UPPERCASE — always pass ingredient and brand names in uppercase (e.g. "APIXABAN" not "apixaban") or you will get 0 results. Returns approval status, sponsor, application number (ANDA = generic, NDA = brand), and application details. There is NO queryable "application_type" field — never add application_type:"ANDA" (it returns 0 results). To limit to generics, search by active ingredient and read the ANDA/NDA prefix on application_number in the results. This endpoint has NO indication/disease field — for "drugs approved to treat <condition>" use fda_drug_labels (which searches indications_and_usage); an indication phrase passed here is silently ignored and matches by drug name only. The response `total` can exceed the 100-row cap on a single page — use `skip` to page past it, and `sort` to get genuinely-newest-first ordering ("most recently approved" is not the default order).fda_applications_by_cikFind ALL Drugs@FDA applications for a company by SEC CIK, ticker, or company name — without needing to know its FDA sponsor_name spelling. Drugs@FDA has no company-ID field: sponsor_name is free text, and one company routinely files under several forms (e.g. Eli Lilly appears as "LILLY", "ELI LILLY AND CO", "ELI LILLY CO", "LILLY RES LABS" — its own SEC-registered name "ELI LILLY AND COMPANY" matches ZERO of them in fda_drug_approvals). This resolves the company via SEC (same identity as the edgar pack), derives its most distinctive name token, and searches Drugs@FDA for every sponsor_name variant containing it in one call — returning the combined application list plus a `sponsor_name_forms` breakdown showing exactly which spellings were found. Use this INSTEAD of guessing sponsor_name strings for fda_drug_approvals when you have (or can resolve) the company's CIK/ticker. For a subsidiary or operating name that isn't itself SEC-listed, resolve to the parent first with edgar's sponsor_to_filer, then pass that CIK here.fda_novel_approvalsMost recent novel drug approvals — the newest drugs approved by the FDA. Use for "what is the most recent novel drug the FDA approved", "latest FDA drug approvals", "recently approved new drugs or biologics this month/year". Returns original NDA/BLA approvals (generics excluded by default) sorted newest-first, with approval date, brand name, active ingredients, sponsor, and application number. Not for label text (fda_drug_labels) or searching a specific known drug (fda_drug_approvals).fda_drug_labelsGet FDA drug labeling (SPL) by drug name OR by INDICATION. This is the tool for "what drugs are approved to treat <condition>" — it searches the indications_and_usage text, which the drugsfda approvals endpoint does NOT carry. Query by brand/generic name (openfda.brand_name:"HUMIRA"), or by indicated use (indications_and_usage:"rheumatoid arthritis"). Returns indications, boxed/other warnings, dosage, contraindications, and adverse reactions (each text field capped, set_id preserved for out-of-band full-label fetch). Note: FDA label publication trails approval by weeks, so a just-approved drug may not have a label yet.fda_drug_recallsSearch FDA drug recalls and enforcement actions by drug name or reason — returns recall classification, date, reason and enforcement status. A multi-word search is tried as ALL terms first and falls back to ANY term when nothing matches all of them; the response says which happened in match_mode, so a loose match is never mistaken for a precise one. Recall reasons are free narrative text and often name the contaminant rather than the harm ("NDMA impurity", not "cancer"), so search the substance when a symptom finds nothing.fda_drug_shortagesSearch the FDA Drug Shortages database by generic or brand name, manufacturer, status, or an advanced openFDA query. Returns national supply records and available FDA dates; reason and other details are sparse in the upstream data. This is not local pharmacy inventory or medical advice.fda_shortage_changesFDA drug-shortage records ordered by update_date, newest first, then restricted to the requested look-back window. Use for recently updated, discontinued, or resolved national shortages; this does not imply availability at any specific pharmacy or hospital. Most rows in any window are "Reverified" (FDA re-checking a status it already had) — pass update_type to filter to the change kinds that actually matter, e.g. New/Discontinued/To Be Discontinued/Resolved, and exclude Reverified.fda_complete_response_lettersSearch FDA-disclosed Complete Response Letters for drug and biologic applications. Defaults to letter_type "COMPLETE RESPONSE"; optionally include other letter types in the same dataset. Returns the application’s current approval_status, letter metadata, an excerpt, and the official document URL.fda_crl_detailRetrieve one FDA Complete Response Letter by application number and optionally letter date. Returns the FDA-disclosed letter text and document URL. Confidential commercial and trade-secret material may be redacted by FDA.fda_food_recallsSearch FDA FOOD recall / enforcement reports (openFDA /food/enforcement) — product recalls, reasons, classification, recalling firm, distribution, and status. Use for food-safety / recall-history questions (distinct from fda_drug_recalls which covers drugs).fda_event_countsAggregate adverse events by reaction type, patient age, or outcome. Returns top reactions for a drug and event trends over time.- +6 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fulcra Context MCP
{
"mcpServers": {
"fulcradynamics-fulcra-context-mcp": {
"command": "uvx",
"args": [
"fulcra-context-mcp@latest"
],
"env": {
"FULCRA_ENVIRONMENT": "YOUR_FULCRA_ENVIRONMENT_HERE"
}
}
}
}
Openfda
{
"mcpServers": {
"openfda": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-openfda"
]
}
}
}
Frequently asked questions
Fulcra Context MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Openfda belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Fulcra Context MCP for biology & bioinformatics work and Openfda for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Fulcra Context MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. Openfda has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fulcradynamics-fulcra-context-mcp and openfda as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fulcra Context MCP has a quality signal of 63/100 (Good) with 5 views, 0 installs and 9 GitHub stars. Openfda has 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars.