Systematic medical reviews and evidence-based healthcare research
Free
Tools
search_literature
Search scientific literature and read full-text content from peer-reviewed papers. Use `dois` (preferred) or `titles` with targeted `term` queries to extract full-text passages from specific papers. Each call returns up to 5 relevant excerpts (~500 chars each) — vary search terms across calls to read through a paper section by section. **IMPORTANT — keep `limit` small.** Use `limit: 10-50` with
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
—
p95 latency
—
call success
—
uptime 90d
0
calls last 7d
What it does
Ground answers in scientific literature. Search full text, evaluate trust, access full-text articles
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add scite-mcp
# 2 — ask your agent something
> Ground answers in scientific literature. Search full text, evaluate trust, access full-text articles
Scite is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
APAll 1 server
api.scite.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --transport http scite-mcp https://api.scite.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
25 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search scientific literature and read full-text content from peer-reviewed papers. Use `dois` (preferred) or `titles` with targeted `term` queries to extract full-text passages from specific papers. Each call returns up to 5 relevant excerpts (~500 chars each) — vary search terms across calls to read through a paper section by section. **IMPORTANT — keep `limit` small.** Use `limit: 10-50` with
Takes no parameters.
Example callreturns →
Search patent families from the scite patents database. Use this tool to find patents related to scientific research topics. Returns patent families with titles, abstracts, inventors, assignees, filing status, and citation counts. **Parameters:** - q: Search query string (keywords, inventor name, assignee, etc.) - f: Space-delimited filters in key:value format (e.g. "assignee:Pfizer filing_statu
Takes no parameters.
Example callreturns →
Search clinical trials from the scite clinical trials database (ClinicalTrials.gov). Use this tool to find clinical trials related to diseases, interventions, sponsors, or research topics. Returns trials with titles, brief descriptions, sponsors, facilities, conditions, interventions, phase, and dates. Highlighted `<strong>...</strong>` snippets indicate which fields matched the query. **Paramet
Takes no parameters.
Example callreturns →
Fetch full details for a single clinical trial by NCT id. Use this after `search_clinical_trials` when you need the complete record for a specific trial, including the full `description`, study `design`, `enrollment`, `outcomes` (primary/secondary), full `eligibility` inclusion/exclusion criteria, `reportedEvents` (adverse events when the trial has posted results), principal investigator (`pi`),
Takes no parameters.
Example callreturns →
Search research grants from the scite grants database (NIH RePORTER, NSF, SBIR/STTR, Wellcome, EU, and more). Use this tool to find grants by research topic, PI, organization, agency, or funding keywords. Returns grants with title, a short abstract preview, agency, organization, PI, country, dates, awardAmount, tags, and externalLink. Highlighted `<strong>...</strong>` fragments indicate which fi
Takes no parameters.
Example callreturns →
Fetch full details for a single grant by id. Call this after `search_grants` only when you need something the search result does not already have. Specifically, this returns: - Full `abstract` (search returns only a ~300-char highlighted preview; the full text is typically 1-3 KB). - Source-specific identifiers that search does not include: `awardYear`, `agencyTrackingNumber`, `contract`, `nih
Takes no parameters.
Example callreturns →
Search FDA 510(k) premarket notification clearances from the scite device database. Use this tool to find medical device clearances by device name, product code, applicant, clearance type, or K number. Returns clearances with device details, decision info, applicant information, and regulatory classifications. 510(k) is the FDA's premarket notification process -- manufacturers must demonstrate t
Takes no parameters.
Example callreturns →
Fetch full details for a single FDA 510(k) clearance by K number. Use this after `search_device510k` when you need the complete record for a specific clearance, including the full `summaryText` (the complete 510(k) summary statement, often very long), full `applicant` details (address, contact, country), `registration` info (FEI and registration numbers), and the complete `decision` object (code,
Takes no parameters.
Example callreturns →
Search the full text of FDA 510(k) summary PDF documents. This dataset contains OCR'd full-text content from FDA 510(k) premarket notification summary PDFs. Unlike `search_device510k` which returns structured clearance metadata (device class, applicant, decision codes), this tool searches the actual narrative text of 510(k) submissions and returns matching page-level snippets. Use this tool when
Takes no parameters.
Example callreturns →
Fetch the full text of a single FDA 510(k) summary PDF by document ID. Use this after `search_510k_summaries` or `search_device510k` when you need the complete narrative text of a 510(k) summary, not just search snippets or structured metadata. Returns the full extracted text organized by page. **Parameters:** - id: Document identifier (the K number, e.g. `K192757`). Can be obtained from either
Takes no parameters.
Example callreturns →
Search MHRA (Medicines and Healthcare products Regulatory Agency) safety alerts and publications. This dataset contains full-text content from MHRA drug safety alerts, medical device alerts, field safety notices, and regulatory publications. Search covers headlines, descriptions, and page-level document content. Use this tool when the question involves UK drug safety communications, MHRA medical
Takes no parameters.
Example callreturns →
Fetch the full text of a single MHRA alert or publication by document ID. Use this after `search_mhra` when you need the complete text of an alert, including the full article body (contentHtml), not just search snippets. Returns the full extracted text organized by page. **Parameters:** - id: Document identifier from `search_mhra` results. **Returns:** The full-text content of the MHRA alert, i
Takes no parameters.
Example callreturns →
Search FDA MAUDE (Manufacturer and User Facility Device Experience) adverse event reports. Use this tool to find medical device adverse event reports, including device malfunctions, patient injuries, and deaths reported to the FDA. Returns reports with device information, event descriptions, patient problems, and narrative text snippets. **Parameters:** - q: Search query string (device name, man
Takes no parameters.
Example callreturns →
Fetch full details for a single MAUDE adverse event report by ID. Use this after `search_maude` when you need the complete record for a specific report, including the full narrative text (MDR text with text type codes), reporter information, device availability, patient treatment, and tags. The search tool returns truncated text snippets; this tool returns the full narratives which can be much lo
Takes no parameters.
Example callreturns →
Search FDA FAERS (FDA Adverse Event Reporting System) drug adverse event reports. Use this tool to find adverse event and medication error reports submitted to the FDA for drugs and therapeutic biologics. Each report links one or more suspect/concomitant drugs to the patient reactions that were observed. Returns reports with the drugs involved, patient reactions (MedDRA preferred terms), seriousn
Takes no parameters.
Example callreturns →
Fetch full details for a single FAERS adverse event report by ID. Use this after `search_faers` when you need the complete record for a specific report, including patient demographics, full drug dosage details, the reporting source, and any duplicate-report references. The search tool returns a slim view; this tool adds detail-only fields. **Parameters:** - id: FAERS safety report ID (e.g. `2618
Takes no parameters.
Example callreturns →
Search FDA drug records: Structured Product Labels, the Orange Book, and Drugs@FDA. Each result bundles an FDA drug application (approved products, applicant, approval dates, marketing status) with its Structured Product Label (indications, warnings, pharmacology, etc.). Use this to find approved drugs by name, active substance, manufacturer, pharmacologic class, or indication. **Parameters:** -
Takes no parameters.
Example callreturns →
Fetch full details for a single FDA drug record by ID. Use this after `search_drugs` when you need the complete record for a specific drug, including every approved product (product number, applicant, approval date, dosage form, route, active ingredients, TE code) and the full Structured Product Label text sections. The search tool returns a slim view; this tool adds detail-only fields. **Parame
Takes no parameters.
Example callreturns →
Create a new Collection owned by the signed-in user. Use this to start a Collection from a list of DOIs the user wants to group, track, and analyze together. The caller becomes the Collection ADMIN. The returned `slug` identifies the Collection for `get_collection`, `update_collection`, `add_dois_to_collection`, and the other Collection tools. **DOI validation.** Provided DOIs are validated and
Takes no parameters.
Example callreturns →
Fetch a single Collection (a saved, named set of papers) by its slug. Use the `slug` returned by `create_collection` or `search_collections`. Returns the Collection's identity, sharing, access level, and DOI counts. The caller must have at least VIEWER access (own it, be shared on it, or it is public). **Parameters:** - slug: The Collection slug (required). **Returns:** The Collection with id,
Takes no parameters.
Example callreturns →
List the Collections the signed-in user can access, with an optional name filter. Returns Collections the user owns, is shared on, or that are shared with their organization. Pass `q` to filter by a case-insensitive substring of the Collection name. This is a filter over the caller's own Collections, not a full-text search of all Collections. **Parameters:** - q: Optional case-insensitive name s
Takes no parameters.
Example callreturns →
Update a DOI-list Collection the signed-in user can edit. Partial update: only the fields you supply change; omitted fields keep their current values. Omitting `dois` leaves the DOI list untouched; supplying `dois` replaces it (unknown DOIs are dropped and surfaced via `unmatchedDoiCount`). Requires EDITOR or ADMIN access. Only DOI-list Collections can be updated here — saved-search Collections a
Takes no parameters.
Example callreturns →
Permanently delete a Collection. Requires ADMIN access on the Collection. This cannot be undone. The Collection and its DOI membership are removed. Only the Collection ADMIN may delete it. **Parameters:** - slug: The Collection slug (required). **Returns:** `{deleted: true, slug: "..."}` on success.
Takes no parameters.
Example callreturns →
Add DOIs to a Collection. Works on both DOI-list and saved-search Collections. Requires EDITOR or ADMIN access. For a DOI-list Collection the DOIs are added to the list. For a saved-search Collection they are force-included (added to the manual include list) so they appear even if the search would not return them. DOIs already present are ignored. Use `create_collection` to make a new Collection
Takes no parameters.
Example callreturns →
Remove DOIs from a Collection. Works on both DOI-list and saved-search Collections. Requires EDITOR or ADMIN access. For a DOI-list Collection the DOIs are dropped from the list. For a saved-search Collection they are excluded (added to the exclude list) so they no longer appear even if the search would return them. DOIs not present are ignored. This removes papers from the Collection; it does no
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Scite costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 1.0.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Scite in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.