Crossref Citation MCP Server
Pricing
from $50.00 / 1,000 tool calls
Crossref Citation MCP Server
An MCP server over the official Crossref REST API (api.crossref.org) — scholarly work
Pricing
from $50.00 / 1,000 tool calls
Rating
0.0
(0)
Developer
NexGen Watch
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
21 hours ago
Last modified
Categories
Share
An MCP server over the official Crossref REST API (api.crossref.org) — scholarly work
metadata and citation counts across registered publishers. Runs as an Apify Standby MCP
server; connect an MCP client to the server URL at path /mcp.
Tools
search_works(query, rows)— search Crossref by free text; returns DOIs, titles, years and citation counts.get_work(doi)— full metadata for one DOI: title, authors, journal, year, publisher, citation and reference counts.get_citation_count(doi)— how many works Crossref records as citing this DOI (is-referenced-by-count).explain_limits()— scope, the meaning of the citation count, and what the server will not assert.
Billing
| Event | Price |
|---|---|
Server start (apify-actor-start) | $0.05, charged once per run by the platform |
Tool call (mcp-tool-call) | $0.05 per completed tool call |
One flat charge per completed tool call. A DOI that Crossref returns 404 for is a sourced answer ("not in Crossref") and is charged; a search matching zero works is charged. A malformed DOI, an empty query, or an upstream Crossref failure is a notice and is not charged.
Source
The Crossref REST API, queried anonymously in the polite pool with a mailto. No API key.
is-referenced-by-count reflects Crossref's coverage (a lower bound), not a universal count.