Openalex Research MCP Server
openalex-research-mcp
npm
v0.5.0
Source verified
Published by oksure — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for OpenAlex API - enabling literature review and research landscaping
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 − 0 = 100. 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:
✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.
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 1
low Hardcoded egress to an external endpoint in packaging/dev tooling (build/setup.js)MTC-SRC-003
In a packaging/dev/install script (shipped, but not the server runtime) (`build/setup.js:138`): 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: const response = await axios.get('https://api.openalex.org/works', { params, timeout: 10000,
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 build/setup.js
Tools 31
Each tool and what it can reach — statically extracted from the published source.
analyze_geographic_distributionno sensitive capabilityanalyze_topic_trendsno sensitive capabilityautocomplete_searchno sensitive capabilitybatch_resolve_referencesno sensitive capabilitycheck_venue_qualityno sensitive capabilitycompare_research_areasno sensitive capabilityfind_open_access_versionno sensitive capabilityfind_review_articlesno sensitive capabilityfind_seminal_papersno sensitive capabilityget_author_collaboratorsno sensitive capability
Show 21 more tools ↓
get_author_profileno sensitive capabilityget_author_worksno sensitive capabilityget_citation_networkno sensitive capabilityget_entityno sensitive capabilityget_related_worksno sensitive capabilityget_top_cited_worksno sensitive capabilityget_top_venues_for_fieldno sensitive capabilityget_trending_topicsno sensitive capabilityget_workno sensitive capabilityget_work_citationsno sensitive capabilityget_work_referencesno sensitive capabilityhealth_checkno sensitive capabilitylist_journal_presetsno sensitive capabilitysearch_authorsno sensitive capabilitysearch_authors_by_expertiseno sensitive capabilitysearch_by_topicno sensitive capabilitysearch_in_journal_listno sensitive capabilitysearch_institutionsno sensitive capabilitysearch_sourcesno sensitive capabilitysearch_worksno sensitive capabilitysearch_works_in_venueno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (31 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.0 latest |
A 100/100 | 1 | 1.13.0 | 2026-09-07 |
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.
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 openalex-research-mcp --onlineMore in Analytics & Monitoring
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.