Compatible with every major AI agent and IDE
What is the NIH RePORTER (Research Funding) MCP Server?
Connect to the NIH RePORTER (Research Portfolio Online Reporting Tools) to explore the vast landscape of NIH-funded research. This server allows AI agents to query project metadata, funding amounts, principal investigators, and publication records directly from the official government database.
What you can do
- Project Discovery — Search for NIH grants and projects using criteria like fiscal years, PI names, organization names, and project numbers.
- Funding Analysis — Retrieve specific award amounts and filter research by agency (e.g., NIGMS, NIAID) or award ranges.
- Publication Tracking — Find scientific publications linked to specific NIH applications or core project numbers using PubMed IDs.
- COVID-19 Research — Filter projects specifically related to COVID-19 responses and supplemental funding.
- Advanced Filtering — Use text searches, date ranges, and organizational matching to find precise research data.
How it works
- Subscribe to this server
- This is a public data service; no private API key is required for standard access, but you can configure your connection to start querying immediately.
- Start analyzing the NIH research portfolio from Claude, Cursor, or any MCP-compatible client.
Who is this for?
- Academic Researchers — quickly find related work, funding history for specific labs, or publication outputs of NIH grants.
- Data Scientists — aggregate funding trends and research outputs for bibliometric or policy analysis.
- Grant Writers & Administrators — research successful grant examples and funding patterns within specific institutions or fields.
Built-in capabilities (2)
Use this to find grants, funding amounts, PIs, and organizations. Search for NIH projects based on specified criteria
Search for publications associated with NIH projects
Why CrewAI?
When paired with CrewAI, NIH RePORTER (Research Funding) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call NIH RePORTER (Research Funding) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
NIH RePORTER (Research Funding) in CrewAI
NIH RePORTER (Research Funding) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect NIH RePORTER (Research Funding) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for NIH RePORTER (Research Funding) in CrewAI
The NIH RePORTER (Research Funding) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 2 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
NIH RePORTER (Research Funding) for CrewAI
Every tool call from CrewAI to the NIH RePORTER (Research Funding) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I find all NIH grants awarded to a specific university?
Use the search_projects tool and provide the university name in the org_names array. You can also refine the search by adding fiscal_years to see awards for a specific period.
Can I see which publications resulted from a specific NIH project number?
Yes! Use the search_publications tool and enter the project identifier in the core_project_nums field. The agent will return a list of associated PubMed records.
Is it possible to filter research projects by funding amount?
Absolutely. The search_projects tool includes an award_amount_range parameter where you can specify min_amount and max_amount to find projects within your budget criteria.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Project Gutenberg
3 toolsUniversal public domain library — search and retrieve thousands of free books via AI.

360dialog
10 toolsSend WhatsApp messages at scale, manage templates, and track delivery with the official 360dialog Business API integration.

YAML/JSON Converter
1 toolsPrevent DevOps YAML hallucination. Convert complex YAML files to JSON for safe AI processing, and back to perfect YAML.

Exa
3 toolsSemantic search engine built for AI — find conceptually relevant web content, not just keyword matches. Powered by neural search technology.
