openalex_mcp_resolve_entity – 1 MCP server offers this tool
What it usually takes
entity_type– in 1 of 1max_results– in 1 of 1query– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
OpenAlex MCP Demo co.huggingface.geraldine/openalex-mcp Resolve a name to an OpenAlex entity — id, external id, and filter key. Free and fast. Backed by /autocomplete, which returns a filter_key alongside each suggestion: the API itself saying which filter that identifier belongs in ("authorships.institutions.lineage" for an institution, "topics.id" for a topic). Run this before filtering on a name. Autocomplete is prefix-based and diacritic-sensitive, and the two combine badly: "strasbourg" alone finds nothing because it is not a prefix of the name, and "universite de stras" finds nothing either because the name is spelled "Université". "université de stras" finds it on the first try. When the prefix match is empty, a widened search is tried and what it finds goes into "suggestions", never into "results", with "error" still set — the caller chooses. Returns: {"source": "openalex", "command": "resolve_entity", "total_found": int, "returned": int, "results": [{"source": "openalex", "id": str, "url": str, "display_name": str, "entity_type": s | entity_type,max_results,query | Not stated |