paperstack-mcp@0.1.9
VERIFIED· not startedPublisher claims: "Model Context Protocol server for arXiv PDF retrieval and LLM context generation." 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
CHUNK_OVERLAP_TOKENSCHUNK_SIZE_TOKENSGITHUB_TOKENS2_API_KEYConfiguration, not credentials: ARXIV_CACHE_DB, ARXIV_DB_PATH, ARXIV_DOWNLOAD_DIR, ARXIV_KEEP_PDFS, ARXIV_MAX_CONCURRENT_DOWNLOADS, ARXIV_MAX_CONCURRENT_PARSERS, ARXIV_MAX_RESULTS, ARXIV_PDF_MAX_PAGES, ARXIV_PDF_MAX_SIZE_MB, ARXIV_RATE_LIMIT_DELAY, CITATION_CACHE_TTL, CONTRIBUTION_CACHE_TTL, DIFF_CACHE_TTL, EMBEDDING_MODEL, GITHUB_MAX_FILE_SIZE_KB, GITHUB_MAX_FILES, HTTP_TIMEOUT, LINK_CACHE_TTL, MAX_RETRIES, OLLAMA_BASE_URL, OLLAMA_MODEL, REPRO_CACHE_TTL, SEMANTIC_INDEX_DIR- Where it talks to
- no vendor host named in the codeAlso arxiv.org, githubusercontent.com, paperswithcode.com, semanticscholar.org — 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 with a scoped credential, under the guard, and read the third-party hosts first. The code names arxiv.org, githubusercontent.com, paperswithcode.com, semanticscholar.org as well as its own vendor. The guard injects CHUNK_OVERLAP_TOKENS, CHUNK_SIZE_TOKENS, GITHUB_TOKEN, S2_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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-14 and scored it 95/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
No findings across 7,885 lines in 55 files.
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 paperstack-mcp@0.1.9 as of 2 h ago. This is the package itself, not its dependencies.