4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
OSTI (DOE Scientific Research) MCP Server

Bring Doe Research
to CrewAI

Learn how to connect OSTI (DOE Scientific Research) to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Data Explorer RecordGet Osti RecordReserve DoiSearch Data Explorer RecordsSearch Osti RecordsSubmit Record

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
OSTI (DOE Scientific Research)

What is the OSTI (DOE Scientific Research) MCP Server?

Connect to the Office of Scientific and Technical Information (OSTI) to query the US Department of Energy's vast research output. This MCP server allows AI agents to navigate millions of research records and datasets through natural conversation.

What you can do

  • Research Search — Query OSTI.GOV for publications, reports, and conference papers using authors, titles, or specific identifiers.
  • Dataset Discovery — Search the DOE Data Explorer specifically for scientific datasets and retrieve detailed metadata for data-driven insights.
  • Record Inspection — Fetch comprehensive bibliographic data and full-text availability for specific records using unique OSTI IDs.
  • DOI Management — Reserve and submit Digital Object Identifiers (DOIs) via the E-Link API for DOE-funded scientific research and data.
  • Advanced Filtering — Narrow down results by sponsoring organization, research organization, or specific publication date ranges.

How it works

  1. Subscribe to this server
  2. (Optional) Enter your OSTI E-Link Token for DOI reservation and submission features
  3. Start searching and analyzing scientific data directly from Claude, Cursor, or any MCP client

Who is this for?

  • Researchers & Academics — quickly find relevant DOE-funded literature and datasets without manual portal searching
  • Data Scientists — discover and inspect metadata for scientific datasets to fuel analysis and modeling
  • Grant Administrators — manage DOI registrations and verify record submissions for funded projects

Built-in capabilities (6)

get_data_explorer_record

Get a single DOE Data Explorer record by ID

get_osti_record

Get a single OSTI.GOV record by ID

reserve_doi

Requires minimal metadata. Reserve a DOI via E-Link API

search_data_explorer_records

Search DOE Data Explorer records (datasets)

search_osti_records

Search OSTI.GOV records

submit_record

Submit/Update a record and register DOI via E-Link API

Why CrewAI?

When paired with CrewAI, OSTI (DOE Scientific Research) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OSTI (DOE Scientific Research) 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 mcps parameter 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

See it in action

OSTI (DOE Scientific Research) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

OSTI (DOE Scientific Research) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect OSTI (DOE Scientific Research) 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for OSTI (DOE Scientific Research) in CrewAI

The OSTI (DOE Scientific Research) 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 6 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.

OSTI (DOE Scientific Research)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures OSTI (DOE Scientific Research) for CrewAI

Every tool call from CrewAI to the OSTI (DOE Scientific Research) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I search for research papers by a specific author?

You can use the search_osti_records tool and provide the author's name in the author parameter. The agent will return a list of matching records from the OSTI.GOV repository.

02

What is the difference between searching OSTI records and Data Explorer records?

Use search_osti_records for general research information like publications and reports. Use search_data_explorer_records specifically when you are looking for scientific datasets.

03

Can I reserve a DOI for my research before it is public?

Yes, if you have an E-Link token, you can use the reserve_doi action. You'll need to provide the title, product type, and your site ownership code.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

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 →