Scholar Feed
MCP server for searching 600,000+ CS/AI research papers with citation graphs, full text, embeddings, and BibTeX. Works with Claude Code, Cursor, and any MCP client. No signup required.
Is Scholar Feed safe? Promising trust profile, but some evidence still deserves review.
Compare Scholar Feed
How does it stack up against its MCP Servers neighbours?
- Reddit MCP Server +0.1 higher
- Openrouter MCP Multimodal same score
- Sonilo Music & Sound Effects 0.2 lower
In detail: Scholar Feed scores 74.6/100 (Grade B), ranked #231 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.3/10; 30% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How Scholar Feed compares in MCP Servers
- #134 Reddit MCP Server 74.7 +0.1
- #135 Openrouter MCP Multimodal 74.6 ±0
- #136 Scholar Feed 74.6 this agent
- #137 Sonilo Music & Sound Effects 74.4 −0.2
- #138 MCP Superset 74.3 −0.3
Bars show each HVTrust score; the tick marks Scholar Feed’s 74.6.
Where the 74.6 comes from
HVTrust dimensions vs the MCP Servers average
74.6 / 100 · 100.0% confidenceScholar Feed MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
53.5 / 100Supply Chain Trust
Common questions about Scholar Feed
Does Scholar Feed publish package provenance?
Does Scholar Feed have an OpenSSF Scorecard?
Is Scholar Feed actively maintained?
What license does Scholar Feed use?
Are Scholar Feed's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Scholar Feed's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Scholar Feed?
For maintainers
HVTrust scores Scholar Feed from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/scholar-feed)
<a href="https://hvtracker.net/agents/scholar-feed"><img src="https://hvtracker.net/badge/scholar-feed.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON