MCP.Market

Openalex MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/openalex·v0.2.1

OpenAlex MCP — wraps the OpenAlex API (scholarly works, free, no auth)

A87/100grade A
What users say
No reviews yet
Be the first
Safety scan
A87/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Openalex yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Openalex tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Openalex compares

Against every graded Security MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 75% of 915 Security servers
Uptime
100%
of our recent checks; the typical remote Security server answers 100%
Response time
107 ms
faster than 85% of 547 Security servers

Release history: 5 versions in the registry since 2026-04-03, latest 2026-11-03, typically one every 32 days.

Install Openalex in Claude Code, Cursor or VS Code

claude mcp add --transport http openalex https://gateway.pipeworx.io/openalex/mcp
Add to Cursor

What the publisher says

From the Openalex repository's README, as published. We do not edit it. Read it on GitHub

OpenAlex — Open Catalog of Scholarly Works

OpenAlex is a free, open replacement for Microsoft Academic Graph (which shut down in 2022). 240M+ scholarly works with structured data on authors, institutions, concepts, citations, and venues. Open-source data model, generous API. Free, no auth (polite User-Agent + email recommended).

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Why this matters for AI agents

Where Semantic Scholar is search-focused and Crossref is DOI-focused, OpenAlex is the most comprehensive structured graph: papers + authors + institutions + funders + concepts, all linked. For institutional analysis, citation networks, or systematic literature review, OpenAlex covers ground the others don't.

Common flows:

  • Work lookup. Find a paper by DOI, title, or OpenAlex ID; get full structured record.
  • Author / institution. Search Yale's CS department's papers in 2024.
  • Concept browsing. Papers tagged with "transformer architecture" or "CRISPR Cas9."
  • Citation graph. "Who cites paper X?" or "What does paper X cite?"

Citable URI: pipeworx://openalex/work/{work_id}.

Auth

Free, public. OpenAlex strongly encourages identifying yourself via mailto= query parameter or User-Agent for "polite pool" priority. Pipeworx forwards mailto=support@pipeworx.io and User-Agent: Pipeworx (mailto:support@pipeworx.io) automatically.

Entity types

OpenAlex models 5 entity types, each with stable IDs:

Works are linked to authors, institutions (where authors are affiliated), venues (where they were published), and concepts (what they're about). Cross-entity queries are powerful.

Common pitfalls

  • Author disambiguation. OpenAlex makes a serious effort but isn't perfect. The same person may have separate Author IDs across early-career vs late-career; common-name authors split across entities. Cross-reference with ORCID where available.
  • Concept hierarchy depth. OpenAlex concepts form a 6-level tree. "Computer science" level 0 is too coarse for most queries; level 3-4 ("transformer model", "BERT model") is more useful.
  • Open access status. OpenAlex tracks oa_status (gold, green, hybrid, bronze, closed). Use it to surface free-to-read versions in your output.
  • Citation count vs. cited-by. OpenAlex computes citation counts from its own corpus. Same paper can show different counts in Google Scholar (broader) and Web of Science (narrower).
  • Lag. New papers appear within weeks. Citations to those papers take longer because citing papers must themselves be indexed.
  • Tied to Semantic Scholar? OpenAlex and Semantic Scholar are separate projects with separate data. Some overlap in coverage; some divergence in metadata. Use both for comprehensive lookups.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "openalex": {
      "url": "https://gateway.pipeworx.io/openalex/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/openalex/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Openalex: common questions

Is Openalex MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Openalex safety report
How do I install Openalex?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Openalex need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Openalex maintained?
The last commit was 40 days ago (2026-09-25). The latest release is v0.2.1.
Is Openalex up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Openalex?
Servers from other publishers that do the same job: Rede MCP server, Raziel MCP server and MyMedi-AI MCP server.
How does Openalex compare with other Security MCP servers?
safety score 87/100 (higher than 75% of 915 Security servers); uptime 100% (of our recent checks; the typical remote Security server answers 100%); response time 107 ms (faster than 85% of 547 Security servers). Full comparison.

Alternatives to Openalex

Same job from other publishers: the closest match first, then the best rated.

  • Rede
    MCP server for Rede — Itaú-owned BR acquirer: authorize/capture/refund, zero-auth, card tokens
    B
  • Raziel
    MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis
    A
  • MyMedi-AI
    DME billing and medical coding: code lookup, DMEPOS fee schedules, Medicare prior-auth checks
    A
  • Healthclaw Guardrails
    Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation
    A
  • spintax.net MCP server
    Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth.
    A

More from pipeworx-io →