Systematic medical reviews and evidence-based healthcare research
Free
Nothing to run from here
Scholar Feed 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for Scholar Feed: search 600,000+ CS/AI/ML papers with LLM-powered analysis
Quickstart
# 1 — run it from where its publisher ships it
npx -y scholar-feed-mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MCP server for Scholar Feed: search 600,000+ CS/AI/ML papers with LLM-powered analysis
Publishernot claimed
YGAll 1 server
ygao20051 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. This one runs on your machine: your client starts Scholar Feed as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve 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 scholar-feed-mcp -- npx -y scholar-feed-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it asks of you
Nothing is required, but it can take SF_API_KEY if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
26 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.
Create a standing watch — evaluated daily against newly-indexed papers, surfacing new matches via the email digest and via check_watches. MUTATES. Get-or-create by name (re-creating with an existing name returns it unchanged — never errors on duplicate). TWO forms: (1) the v2 STRUCTURED filter via
Takes no parameters.
Example callreturns →
List the authenticated user
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Delete a watch, addressed by watch_id OR name. MUTATES. Idempotent: deleting a non-existent watch is a no-op (no error). To change a watch in place (rename / novelty_min / retarget criteria) use update_watch instead of delete-and-recreate. Requires SF_API_KEY.
Takes no parameters.
Example callreturns →
Update an existing watch in place — rename, change novelty_min, or RETARGET its structured filter
Takes no parameters.
Example callreturns →
Dry-run a structured filter over recent papers WITHOUT creating a watch — the tuning loop. Returns {window_days, needs_similarity, match_count, sample} so you can iterate (add a category, raise min_novelty, switch the collection relation) before saving with create_watch. Structured watches rank by
Takes no parameters.
Example callreturns →
Answer a question using ONLY the papers you
Takes no parameters.
Example callreturns →
Answers
Takes no parameters.
Example callreturns →
Get the citation graph for a paper, sorted by citing-paper rank_score (highest-impact first).
Takes no parameters.
Example callreturns →
Find the co-authorship neighborhood of one or more authors. Given a list of author_ids, returns edges {from, to, papers_count, last_collab_year} where
Takes no parameters.
Example callreturns →
List the authenticated user
Takes no parameters.
Example callreturns →
Create a new named collection. MUTATES. If a collection with that name already exists, returns the existing one (get-or-create — never errors on duplicate). Use
Takes no parameters.
Example callreturns →
Add a paper to a collection, addressed by collection_id OR collection_name (get-or-create by name — no need to look up an id first). Nest with
Takes no parameters.
Example callreturns →
Remove a paper from a collection, addressed by collection_id OR collection_name. MUTATES (the paper stays in your library; it
Takes no parameters.
Example callreturns →
Embed a text string into a 768-dim Gemini Flash vector. Use for HyDE-style retrieval: (1) write a hypothetical short paper that would perfectly answer the user
Takes no parameters.
Example callreturns →
Two-mode author tool — replaces discover_authors and get_author. Provide exactly one of q or id. Q-MODE (q=...): search for researchers by topic or name — uses embedding similarity for topics (
Takes no parameters.
Example callreturns →
Extract paper content from an arXiv paper
Takes no parameters.
Example callreturns →
Find important work you HAVEN
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Returns the FOUNDATIONAL WORK FOR A PAPER
Takes no parameters.
Example callreturns →
Get full details for one or more papers by arXiv ID. Pass a single-element array for one paper; pass multiple IDs to batch-fetch up to 50 papers in one call (replaces the removed batch_lookup tool). Pass format=
Takes no parameters.
Example callreturns →
Save a paper to the authenticated user
Takes no parameters.
Example callreturns →
Remove a paper from the authenticated user
Takes no parameters.
Example callreturns →
Like a paper — a
Takes no parameters.
Example callreturns →
List the authenticated user
Takes no parameters.
Example callreturns →
Search Scholar Feed
Takes no parameters.
Example callreturns →
Standardmost installed
$25 / month
- 20,000 calls a month, included
- 240 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Team
$65 / month
- 150,000 calls a month, included
- 1,800 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $25 a month covers every tool 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
ATrust score 94 / 100
Release 3.13.2 · scanned 25 Aug 2026
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.
Threat score100
Client score94
Findings0 threat · 2 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digestef31ca3b6387964ae9c67eb527d8765f4b76920f3c5bafcbe5ad2afc6fa95527
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestef31ca3b6387964a
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 3.13.2 — 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.
3.13.2
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 Scholar Feed 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.