Paper Search MCP Server

paper-search-mcp PyPI v0.1.4

Published by openags — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A MCP server for searching and downloading academic papers from multiple sources.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 10

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_base.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_base.py:11`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get( "https://api.base-search.net/cgi-bin/BaseHttpSearchInterface.fcgi",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_base.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_biorxiv.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_biorxiv.py:9`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get("https://api.biorxiv.org/details/biorxiv/0/1", timeout=5) return response.s

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_biorxiv.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_citeseerx.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_citeseerx.py:11`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get( "https://citeseerx.ist.psu.edu/api/search", params={"q": "

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_citeseerx.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_crossref.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_crossref.py:11`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get("https://api.crossref.org/works?sample=1", timeout=5) return response.statu

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_crossref.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_dblp.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_dblp.py:12`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: uery response = requests.get( "https://dblp.org/search/publ/api", params={'q': 'test', '

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_dblp.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_doaj.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_doaj.py:10`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get( "https://doaj.org/api/search/articles/machine%20learning",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_doaj.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_google_scholar.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_google_scholar.py:9`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get("https://scholar.google.com", timeout=5) return response.status_code == 200

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_google_scholar.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_hal.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_hal.py:10`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get( "https://api.archives-ouvertes.fr/search/", params={"q": "

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_hal.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_iacr.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_iacr.py:10`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get("https://eprint.iacr.org", timeout=5) return response.status_code == 200

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_iacr.py

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_medrxiv.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_medrxiv.py:9`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get("https://api.medRxiv.org/details/medrxiv/0/1", timeout=5) return response.s

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_medrxiv.py

Tools 63

Each tool and what it can reach — statically extracted from the published source.

  • download_acmingests untrusted input
  • download_arxivingests untrusted input
  • download_baseingests untrusted input
  • download_biorxivingests untrusted input
  • download_citeseerxingests untrusted input
  • download_crossrefingests untrusted input
  • download_dblpingests untrusted input
  • download_doajingests untrusted input
  • download_halingests untrusted input
  • download_iacringests untrusted input
Show 53 more tools ↓
  • download_ieeeingests untrusted input
  • download_medrxivingests untrusted input
  • download_openaireingests untrusted input
  • download_openalexingests untrusted input
  • download_pubmedingests untrusted input
  • download_scihubingests untrusted input
  • download_semanticingests untrusted input
  • download_ssrningests untrusted input
  • download_with_fallbackingests untrusted input
  • download_zenodoingests untrusted input
  • read_acm_paperingests untrusted input
  • read_ieee_paperingests untrusted input
  • search_iacringests untrusted input
  • search_ssrningests untrusted input
  • get_crossref_paper_by_doino sensitive capability
  • read_arxiv_paperno sensitive capability
  • read_base_paperno sensitive capability
  • read_biorxiv_paperno sensitive capability
  • read_citeseerx_paperno sensitive capability
  • read_crossref_paperno sensitive capability
  • read_dblp_paperno sensitive capability
  • read_doaj_paperno sensitive capability
  • read_hal_paperno sensitive capability
  • read_iacr_paperno sensitive capability
  • read_medrxiv_paperno sensitive capability
  • read_openaire_paperno sensitive capability
  • read_openalex_paperno sensitive capability
  • read_pubmed_paperno sensitive capability
  • read_semantic_paperno sensitive capability
  • read_ssrn_paperno sensitive capability
  • read_zenodo_paperno sensitive capability
  • search_acmno sensitive capability
  • search_arxivno sensitive capability
  • search_baseno sensitive capability
  • search_biorxivno sensitive capability
  • search_citeseerxno sensitive capability
  • search_coreno sensitive capability
  • search_crossrefno sensitive capability
  • search_dblpno sensitive capability
  • search_doajno sensitive capability
  • search_europepmcno sensitive capability
  • search_google_scholarno sensitive capability
  • search_halno sensitive capability
  • search_ieeeno sensitive capability
  • search_medrxivno sensitive capability
  • search_openaireno sensitive capability
  • search_openalexno sensitive capability
  • search_papersno sensitive capability
  • search_pmcno sensitive capability
  • search_pubmedno sensitive capability
  • search_semanticno sensitive capability
  • search_unpaywallno sensitive capability
  • search_zenodono sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.4 latest A 96/100 10 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/paper-search-mcp/badge.svg)](https://mcptrustchecker.com/registry/paper-search-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/paper-search-mcp"><img src="https://mcptrustchecker.com/registry/paper-search-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/paper-search-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan paper-search-mcp --online --registry pypi

Use the free API → How scoring works

More in Web, Search & Scraping