openalex-mcp-server
io.github.cyanheads/openalex-mcp-servercyanheadsstreamable-httpv0.11.2Scanned
Access the OpenAlex academic research catalog — 270M+ publications.
5 tools: 5 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the openalex-mcp-server can do
The openalex-mcp-server is published by the GitHub account cyanheads. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
4 tools bring in text other people can write (openalex_resolve_name, openalex_search_entities, openalex_analyze_trends and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 0.11.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
openalex_analyze_trendsAggregate OpenAlex entities into groups and count them.Reads text others writeNo findings
Why it is in this group
- The name "openalex_analyze_trends" says "analyze": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Aggregate OpenAlex entities into groups and count them. Use for trend analysis (group works by publication_year), distribution analysis (group by oa_status, type, country), and comparative analysis (group by institution or topic). Combine with filters to scope the analysis. Returns up to 200 groups per page — use order "key" and cursor pagination for fields with many distinct values. OpenAlex can wrap a key-ordered walk to earlier groups. Stop when a page's first key repeats an earlier key, or when a page is short or empty.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
openalex_describe_fieldsList valid field names for an OpenAlex entity type and context (filter, group_by, or select).No findings
Why it is in this group
- The name "openalex_describe_fields" says "describe": a word for reading.
Description, as the server wrote it List valid field names for an OpenAlex entity type and context (filter, group_by, or select). Use proactively before constructing a filter or group_by to avoid invalid-field 400 errors. Pass `query` to rank the list by name similarity — useful when you have a partial or guessed field name. Ranking never drops a field: the full list comes back either way.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openalex_get_citation_graphWalk the citation graph one hop from a seed work.Reads text others writeNo findings
Why it is in this group
- The name "openalex_get_citation_graph" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Walk the citation graph one hop from a seed work. Direction picks the edge: incoming citations (`cites`), the seed's own references (`cited_by`), or OpenAlex's algorithmically-related works (`related_to`). Note: `direction` follows OpenAlex's filter convention, which inverts the common English reading — `cites` returns works that cite the seed; `cited_by` returns works the seed cites. Results use the works schema; combine with filters/sort to narrow further. A page holds `per_page` works and `next_cursor` continues it.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
openalex_resolve_nameResolve a name or an identifier to an OpenAlex ID.Reads text others writeNo findings
Why it is in this group
- The name "openalex_resolve_name" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Resolve a name or an identifier to an OpenAlex ID. ALWAYS use this before filtering by entity — names are ambiguous, IDs are not. A name returns up to 10 autocomplete matches with disambiguation hints. An identifier — OpenAlex ID, DOI, ORCID, ROR, PMID, PMCID, ISSN, or arXiv ID, bare or in URL form — resolves directly to the record it addresses instead of running a name search. An arXiv ID resolves to its work under any entity_type, found by its arXiv landing page when OpenAlex holds no work under its arXiv DOI, one billed list request. Short names share the bare OpenAlex ID shape (keyword p53 reads as publisher ID P53), so a bare OpenAlex ID that resolves nothing is searched as a name next. Two identifiers can address more than one entity type: a ROR names an organization's institution, funder, and publisher records alike, so it returns each one that exists (institution first) unless entity_type picks one of those three; and a Crossref Funder Registry DOI (10.13039/…) resolves to the funder unless entity_type is works. An award ID (G…, bare or as an OpenAlex URL) is not looked up, since OpenAlex has no award autocomplete: it returns no matches and a notice naming the openalex_search_entities call that opens the award. Under entity_type, a bare G… is searched as a name of that type instead.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
openalex_search_entitiesSearch, filter, sort, or retrieve by ID.Reads text others writeNo findings
Why it is in this group
- The name "openalex_search_entities" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search, filter, sort, or retrieve by ID. Covers all OpenAlex entity types (works, authors, sources, institutions, topics, keywords, publishers, funders, awards). Pass `id` to retrieve a single entity; on works it also takes an arXiv ID, found by its arXiv landing page when OpenAlex holds no work under its arXiv DOI, one billed list request. Otherwise, use `query` and/or `filters` for discovery. Filters take a record object; an unambiguous native string such as "primary_location.source.issn:0920-8542" is also accepted when enabled and disclosed in `notice`. Native clauses split on commas outside paired double quotes and the first colon; duplicate keys and bare fragments are rejected. Any filter value sent unquoted must have paired double quotes; balanced search phrases remain valid. Supports keyword search with boolean operators, exact phrase matching, AI semantic search, and seeded random samples. On works, wildcards (`*`, `?`) need search_mode "exact" or a `.search.exact` filter, and a `*` needs three characters before it. Use openalex_resolve_name to resolve names to IDs before filtering. Searches and ID lookups return a curated set of fields by default; pass `select` (an array, or a comma-separated string) to override with specific fields, or `["*"]` for the full record. A page holds `per_page` records and `next_cursor` continues it — semantic search and a seeded `sample` continue with `page` instead; an `id` lookup returns every selected array whole, and `slice` pages one array by count.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:33 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:openalex_analyze_trendsOnly readsinputSchema
- Changed:openalex_get_citation_graphOnly readsinputSchema
- Changed:openalex_resolve_nameOnly readsdescriptioninputSchema
- Changed:openalex_search_entitiesOnly readsdescriptioninputSchema
Tools5 changed.~5 changedView diff
- Changed:openalex_analyze_trendsOnly readsinputSchema
- Changed:openalex_describe_fieldsOnly readsinputSchema
- Changed:openalex_get_citation_graphOnly readsdescriptioninputSchema
- Changed:openalex_resolve_nameOnly readsdescriptioninputSchema
- Changed:openalex_search_entitiesOnly readsdescriptioninputSchema
Tools4 changed.~4 changedView diff
- Changed:openalex_analyze_trendsOnly readsdescriptioninputSchema
- Changed:openalex_get_citation_graphOnly readsinputSchema
- Changed:openalex_resolve_nameOnly readsinputSchema
- Changed:openalex_search_entitiesOnly readsdescriptioninputSchema
Install
Pinned to version 0.11.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http openalex https://openalex.caseyjhand.com/mcpclaude mcp add --transport http openalex https://openalex.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__openalex__openalex_resolve_name",
"mcp__openalex__openalex_search_entities",
"mcp__openalex__openalex_analyze_trends",
"mcp__openalex__openalex_get_citation_graph",
"mcp__openalex__openalex_describe_fields"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as openalex. Review it before you use it.
Capability tags behind 4 rules
- mcp__openalex__openalex_resolve_name untrusted-input
- mcp__openalex__openalex_search_entities untrusted-input
- mcp__openalex__openalex_analyze_trends untrusted-input
- mcp__openalex__openalex_get_citation_graph untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/openalex-mcp-server/verify?hash=d21fe701bb7a0d5880ca052c92fbd940e201f86394afbad092ce425e157c6ecd" | jq -e '.changed == false'Pinned hash d21fe701bb7a, from Nov 18, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/openalex-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/openalex-mcp-server)Source: MCP Registry · repository. Synced Nov 18, 2026, 07:17 UTC.
openalex-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the openalex-mcp-server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the openalex-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the openalex-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the openalex-mcp-server have?
- 5 tools: 5 read. openalex_resolve_name, openalex_search_entities, openalex_analyze_trends, openalex_get_citation_graph and openalex_describe_fields.
Does the openalex-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the openalex-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the openalex-mcp-server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.