mcp-scholarly@0.1.0
VERIFIED· not startedPublisher claims: "A MCP server to search for accurate academic articles." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso pypa.io, python.org, git-scm.com, gmane.org, aka.ms, microsoft.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-08 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
result = subprocess.run([uv_bin] + args, stdout=subprocess.PIPE)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.check_output(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.completed_process = subprocess.run([uv, *sys.argv[1:]], env=env)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.<summary>Published Docker Servers Configuration</summary> ``` "mcpServers": { "mcp-scholarly": { "command": "docker", "args": [ "run", "--rm", "-i", "mcp/scholaFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.path = subprocess.check_output([Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.<summary>Development/Unpublished Servers Configuration</summary> ``` "mcpServers": { "mcp-scholarly": { "command": "uv", "args": [ "--directory", "/Users/adityaFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-scholarly@0.1.0 as of 6d ago. This is the package itself, not its dependencies.