4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
FOIA.gov (Freedom of Information) MCP Server

Bring Transparency
to CrewAI

Learn how to connect FOIA.gov (Freedom of Information) to CrewAI and start using 4 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 Agency ComponentGet Agency Component Request FormGet Annual Report XmlList Agency Components

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
FOIA.gov (Freedom of Information)

What is the FOIA.gov (Freedom of Information) MCP Server?

Connect to the FOIA.gov API to streamline access to Freedom of Information Act data. This MCP server allows AI agents to navigate the complex structure of US government agencies and their specific FOIA requirements through natural conversation.

What you can do

  • Agency Discovery — List all FOIA agency components and filter by specific fields like titles and abbreviations.
  • Component Details — Fetch deep metadata for specific agency components using their unique UUIDs.
  • Request Forms — Retrieve the exact structure and fields required for FOIA request forms for any specific component.
  • Annual Reports — Access NIEM-standard XML annual reports for agencies by year to analyze transparency metrics.

How it works

  1. Subscribe to this server
  2. Enter your FOIA.gov API Key
  3. Start querying government transparency data from your AI assistant

Who is this for?

  • Journalists & Researchers — quickly identify which agency components handle specific types of records.
  • Legal Professionals — automate the retrieval of request form structures to ensure compliance with agency-specific requirements.
  • Data Analysts — pull annual report data in XML format for large-scale transparency analysis.

Built-in capabilities (4)

get_agency_component

Fetch a specific agency component by UUID

get_agency_component_request_form

Fetch the FOIA request form structure for a specific component

get_annual_report_xml

Fetch an agency annual report in XML format

list_agency_components

Supports JSON API sparse fieldsets and includes. List all FOIA agency components

Why CrewAI?

When paired with CrewAI, FOIA.gov (Freedom of Information) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FOIA.gov (Freedom of Information) 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

FOIA.gov (Freedom of Information) in CrewAI

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

FOIA.gov (Freedom of Information) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect FOIA.gov (Freedom of Information) 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 FOIA.gov (Freedom of Information) in CrewAI

The FOIA.gov (Freedom of Information) 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 4 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.

FOIA.gov (Freedom of Information)
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 FOIA.gov (Freedom of Information) for CrewAI

Every tool call from CrewAI to the FOIA.gov (Freedom of Information) 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 find the specific requirements for filing a FOIA request with an agency?

You can use the get_agency_component_request_form tool with the agency's UUID. It will return the full structure of the form, including all required fields and instructions.

02

Is it possible to list all sub-components of a major government agency?

Yes. Use list_agency_components and you can include the parent agency information to filter or identify all components belonging to a specific department.

03

Can I access the raw annual transparency reports for data analysis?

Absolutely. The get_annual_report_xml tool allows you to fetch the official NIEM-standard XML reports for any agency and year (e.g., DOJ, 2021).

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 →