Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Liyux3/scholar-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/liyux3/scholar-mcp/scholar-mcp-scholar)<a href="https://agentmods.dev/mcp/liyux3/scholar-mcp/scholar-mcp-scholar"><img src="https://agentmods.dev/badge/mcp/liyux3/scholar-mcp/scholar-mcp-scholar/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/liyux3/scholar-mcp/scholar-mcp-scholar"><img src="https://agentmods.dev/badge/mcp/liyux3/scholar-mcp/scholar-mcp-scholar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
scholar scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"scholar": {
"command": "uvx",
"args": [
"--from",
"scholar-mcp==0.8.4",
"scholar-mcp"
],
"env": {
"SCHOLAR_MCP_EXTENSIONS": "research"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 13 lines scan A 4ef70d2d6cdf
scholar is an MCP server published in the GitHub repository Liyux3/scholar-mcp (2 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other mcp servers, from other repositories
patent-literature-search-mcp
Search 200M+ patents and 216M+ scientific papers using natural language and structured filters. Remote server at connect.patsnap.com.
noodle
MCP server "noodle", hosted remotely at api.helena.bio, as configured in helena-bioinformatics/noodle-mcp.
paper-search
Scientific paper search and ranking across OpenAlex, Semantic Scholar, and Unpaywall. Runs locally from the paper-search Python package.
noodle
Search biomedical papers, inspect publication records, and traverse citation or semantic graphs. Remote server at api.helena.bio.
chemistry
The fast, Pythonic way to build MCP servers and clients. Runs locally from the fastmcp Python package.
cdc-health-mcp-server
Search and query CDC public health data — mortality, vaccinations, surveillance, behavioral risk. Runs locally from the @cyanheads/cdc-health-mcp-server npm package. Needs 2 environment variables to run.