zenodo.records.search
Search 3.5M+ open-access research outputs on Zenodo — publications, datasets, software, presentations, posters, videos, and more. Filter by type, access right (open/embargoed/restricted), and publication date range. Sort by relevance, recency, most-viewed, or most-downloaded. Each result includes...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/zenodo.records.search.md
What zenodo.records.search does on Apibase
AI agents call zenodo.records.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number for pagination (default 1). Combine with limit for paging. |
sort | string | — | Sort order: "bestmatch" (relevance), "mostrecent" (newest first), "mostviewed", or "mostdownloaded". Default: bestmatch. |
type | string | — | Filter by record type: "publication" (papers/preprints), "dataset", "software", "presentation", "poster", "image", "video", "lesson", "physicalobject", or "othe |
limit | integer | — | Number of results to return per page (default 10, max 50). |
query | string | — | Free-text search query across title, description, creators, and keywords (e.g. "CRISPR gene editing", "climate change datasets", "machine learning"). |
date_to | string | — | Filter records published on or before this date in ISO 8601 format (e.g. "2024-12-31"). |
date_from | string | — | Filter records published on or after this date in ISO 8601 format (e.g. "2023-01-01"). |
access_right | string | — | Filter by access right: "open" (freely downloadable), "embargoed", "restricted", or "closed". |
Parameters from the server's own tool schema.
Why zenodo.records.search is rated Low
Queries public research metadata with no side effects or data modification capabilities.
From the tool's definition Search 3.5M+ open-access research outputs; retrieves metadata, DOI, title, creators, URL.
Attacks that exploit this kind of access
The rule that runs zenodo.records.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zenodo.records.search, this is the rule to start with:
zenodo.records.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every zenodo.records.search call is checked against it from then on.
Questions about zenodo.records.search
Search 3.5M+ open-access research outputs on Zenodo — publications, datasets, software, presentations, posters, videos, and more. Filter by type, access right (open/embargoed/restricted), and publication date range. Sort by relevance, recency, most-viewed, or most-downloaded. Each result includes DOI, title, creators, resource type, access right, keywords, view/download stats, and a direct URL. Zenodo is operated by CERN under the OpenAIRE program and hosts research from EU-funded projects, science institutions worldwide, and individual researchers. All metadata is CC0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
zenodo.records.search accepts 8 parameters: page, sort, type, limit, query, date_to, date_from, access_right. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for zenodo.records.search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
zenodo.records.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zenodo.records.search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for zenodo.records.search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
zenodo.records.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue