cordis.research.project_search
Search 80,000+ EU-funded research projects from Horizon Europe (2021–2027) and H2020 (2014–2020) using the CORDIS EURIO linked-data SPARQL endpoint. Filter by keywords in the project title, lifecycle status (SIGNED = active, CLOSED = completed, TERMINATED = cancelled), and start year range. Retur...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cordis.research.project-search.md
What cordis.research.project_search does on Apibase
AI agents call cordis.research.project_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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (1-20, default 10) |
query | string | Yes | Keyword(s) to search in project titles (e.g. "artificial intelligence", "climate change", "renewable energy") |
status | string | — | Project lifecycle status filter. SIGNED = active/running, CLOSED = completed, TERMINATED = cancelled early. |
year_to | integer | — | Filter projects starting on or before this year (e.g. 2027) |
year_from | integer | — | Filter projects starting on or after this year (e.g. 2020 for Horizon Europe era) |
Parameters from the server's own tool schema.
Why cordis.research.project_search is rated Low
Tool queries a public research database without modifying, deleting, or executing code.
From the tool's definition Search 80,000+ EU-funded research projects, filter by keywords, returns project metadata.
Attacks that exploit this kind of access
The rule that runs cordis.research.project_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 cordis.research.project_search, this is the rule to start with:
cordis.research.project_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 cordis.research.project_search call is checked against it from then on.
Questions about cordis.research.project_search
Search 80,000+ EU-funded research projects from Horizon Europe (2021–2027) and H2020 (2014–2020) using the CORDIS EURIO linked-data SPARQL endpoint. Filter by keywords in the project title, lifecycle status (SIGNED = active, CLOSED = completed, TERMINATED = cancelled), and start year range. Returns grant agreement ID, RCN, title, dates, and status. Use the id field with cordis.research.project_details to get full project data. Covers research in AI, climate, health, energy, space, digital, and all Horizon thematic clusters. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cordis.research.project_search accepts 5 parameters: limit, query, status, year_to, year_from. Required: query. 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 cordis.research.project_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.
cordis.research.project_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 cordis.research.project_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 cordis.research.project_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.
cordis.research.project_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