Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Scite is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Ground answers in scientific literature. Search full text, evaluate trust, access full-text articles
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http scite-mcp https://api.scite.ai/mcp
# 2 — ask your agent for something these tools do
# search_literature, search_patents, search_clinical_trials and 22 more
Scite costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http scite-mcp https://api.scite.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | no | Cross-field search query. Optional when dois or titles is provided (omit to fetch metadata only). IMPORTANT: Use domain-specific technical terms, not broad phrases — the index covers all academic |
| dois | array | no | Filter results to specific DOIs. Use WITHOUT term to fetch paper metadata (title, abstract, citations, access URL). Use WITH term to search within those papers for full-text excerpts. Prefer DOIs |
| titles | array | no | Filter results to papers matching these titles. Use WITHOUT term to fetch paper metadata, or WITH term to search within those papers. Use when DOIs are not available — prefer dois when possible. |
| limit | integer | no | Maximum number of results to return. Default: 10, Maximum: 1000. For better performance, use smaller limits (10-50) and pagination. |
| offset | integer | no | Pagination offset for result sets. Use with limit for pagination. Example: offset=20, limit=10 returns results 21-30. |
| title | string | no | Filter by text in publication title. Example: 'climate change' |
| abstract | string | no | Filter by text in publication abstract. Example: 'neural networks' |
| author | string | no | Filter by author name. Partial names work. Example: 'Einstein' or 'Albert Einstein' |
| journal | string | no | Filter by journal name. Example: 'Nature' or 'Science' |
| publisher | string | no | Filter by publisher name. Example: 'Elsevier' or 'Springer' |
| year | integer | no | Filter by specific publication year. Example: 2020. Cannot be combined with date_from/date_to. |
| date_from | string | no | Filter papers published from this date onwards. Format: YYYY-MM-DD or YYYY. Example: '2015-01-01' or '2015' |
| date_to | string | no | Filter papers published up to this date. Format: YYYY-MM-DD or YYYY. Example: '2023-12-31' or '2023' |
| paper_type | string | no | Filter by publication type. Examples: 'Article', 'Review', 'Clinical Trial', 'Meta-Analysis', 'Case Report' |
| affiliation | string | no | Filter by author institutional affiliation. Example: 'Stanford University' or 'MIT' |
| topic | string | no | Filter by research topic/subject area. Example: 'Oncology' or 'Neuroscience' |
| has_tally | boolean | no | Filter papers with Smart Citations (tally > 0). true = papers that have been cited with context |
| has_retraction | boolean | no | Filter papers with retraction notices. true = retracted papers only |
| has_concern | boolean | no | Filter papers with editorial concerns. true = papers with concerns |
| has_correction | boolean | no | Filter papers with corrections. true = papers with published corrections |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (keywords, inventor, assignee, CPC code, etc.) |
| f | string | no | Space-delimited filters in key:value format. Example: 'assignee:Pfizer filing_status:granted' |
| p | integer | no | Page number (default: 1) |
| s | string | no | Sort field (default: _relevance) |
| sortDir | string | no | Sort direction (default: desc). Ignored when s is _relevance. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (keywords, condition, intervention, sponsor, NCT id, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. Example: 'conditions:"Cancer" trialState.phase:"Phase III"' |
| p | integer | no | Page number (default: 1) |
| s | string | no | Sort field (default: _relevance) |
| sortDir | string | no | Sort direction (default: desc). Ignored when s is _relevance. |
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),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | NCT identifier of the clinical trial, e.g. NCT02986230. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (keywords, PI name, organization, agency, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. Example: 'agency:"NIH" country:"United States"' |
| p | integer | no | Page number (default: 1) |
| s | string | no | Sort field (default: _relevance) |
| sortDir | string | no | Sort direction (default: desc). Ignored when s is _relevance. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Grant identifier returned by search_grants, e.g. 5201339 or nsf.0646294. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (device name, product code, applicant, K number, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. Example: 'device.deviceClass:"2" decision.decisionCode:"SESE"' |
| p | integer | no | Page number (default: 1) |
| s | string | no | Sort field (default: _relevance) |
| sortDir | string | no | Sort direction (default: desc). Ignored when s is _relevance. |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | K number identifier of the 510(k) clearance, e.g. K210674. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (technical terms, device descriptions, test methods, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. |
| p | integer | no | Page number (default: 1) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document identifier, e.g. K192757. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (drug names, device types, safety issues, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. Facet fields: ontology.tags, ontology.categories, domain. Date range: use attachments.file.createdAt or attachments.file.modifiedAt with gte/lt suffi |
| p | integer | no | Page number (default: 1) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document identifier from search_mhra results. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (device name, manufacturer, event description, product code, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. Facet fields: event_type, device.device_class, device.manufacturer_d_name, device.device_report_product_code, device.regulation_number, report_source |
| p | integer | no | Page number (default: 1) |
| s | string | no | Sort field (default: _relevance) |
| sortDir | string | no | Sort direction (default: desc). Ignored when s is _relevance. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | MAUDE report ID (e.g. '17343805') |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (drug name, active substance, reaction term, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. Facet fields: drug.medicinalproduct, drug.brand_name, drug.generic_name, drug.substance_name, drug.manufacturer_name, drug.drugindication, drug.pharm |
| p | integer | no | Page number (default: 1) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | FAERS safety report ID (e.g. '26185565') |
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: -
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search query (brand name, generic name, active substance, indication, etc.) |
| f | string | no | Space-delimited filters in field:"value" format. Facet fields: labels.brand_name, labels.generic_name, labels.substance_name, labels.manufacturer_name, labels.product_type, labels.route, labels.phar |
| p | integer | no | Page number (default: 1) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Drug record ID (UUID from search_drugs results, e.g. '4dd865ec-8889-49ac-8c8f-4438875937ac') |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Collection name |
| description | string | no | Optional description |
| dois | array | no | Optional list of DOIs to seed the Collection, e.g. ['10.1038/s41586-020-2649-2'] |
| is_public | boolean | no | If true, anyone with the slug can view (default: false) |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The Collection slug |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Optional case-insensitive name substring filter |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The Collection slug |
| name | string | no | New Collection name |
| description | string | no | New description |
| dois | array | no | Replacement DOI list (omit to leave DOIs unchanged), e.g. ['10.1038/s41586-020-2649-2'] |
| is_public | boolean | no | If true, anyone with the slug can view |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The Collection slug |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The Collection slug |
| dois | array | yes | List of DOIs to add, e.g. ['10.1038/s41586-020-2649-2'] |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The Collection slug |
| dois | array | yes | List of DOIs to remove, e.g. ['10.1038/s41586-020-2649-2'] |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Scite or to call it, at any volume.
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 an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Scite can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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 a signed-in account that does not publish it, and nothing else.