ScholarlySAFE
A MCP server to search for accurate academic articles.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://mseep.ai/app/adityak74-mcp-scholarly)
[](https://smithery.ai/server/mcp-scholarly)
A MCP server to search for accurate academic articles. More scholarly vendors will be added soon.
Search tools
search-arxiv— arXiv search (no key needed)search-google-scholar— Google Scholar via thescholarlylibrary (free proxy pool)search-google-web— Google web search via the SerpBase API. Optional; only registered whenSERPBASE_API_KEYis set. Get a key at https://serpbase.dev/dashboard/api-keys (free tier available).
Components
Tools
The server implements one tool:
- search-arxiv: Search arxiv for articles related to the given keyword.
- Takes "keyword" as required string arguments
Quickstart
Install
Claude Desktop
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json
Development/Unpublished Servers Configuration
"mcpServers": {
"mcp-scholarly": {
"command": "uv",
"args": [
"--directory",
"/Users/adityakarnam/PycharmProjects/mcp-scholarly/mcp-scholarly",
"run",
"mcp-scholarly"
]
}
}Published Servers Configuration
"mcpServers": {
"mcp-scholarly": {
"command": "uvx",
"are07c72a69449OBSERVED · 2026-10-06Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-scholarly --env SERPBASE_API_KEY=${SERPBASE_API_KEY} -- uvx mcp-scholarly{
"mcpServers": {
"mcp-scholarly": {
"command": "uvx",
"args": [
"mcp-scholarly"
],
"env": {
"SERPBASE_API_KEY": "${SERPBASE_API_KEY}"
}
}
}
}Exposed tools (1)
1 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
search-google-scholar | read | if not keyword: |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
e07c72a69449full audit observations/trust-audit/mcp-server/adityak74__scholarly.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-06 | e07c72a69449 | SAFE | B | 89 | first audit |
Questions
What is the Scholarly MCP server?
A MCP server to search for accurate academic articles.
What tools does Scholarly expose?
1 in total: 1 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Scholarly safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Scholarly need?
It reads SERPBASE_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Scholarly run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as mcp-scholarly.
How current is this page?
The grade is for one exact copy of the source (e07c72a69449), read on 2026-10-06. The repository is watched and re-audited when it changes.