Is an API key required?

No! The USGS FDSNWS Event API is completely open and requires zero authentication, making this one of the most accessible and powerful real-time data sources available.

What is the query limit?

The maximum number of events returned per single API query is 20,000. If your time range or boundaries are too wide, the API will fail. Use the `count` tool first on large searches.

How fast is the data updated?

The USGS typically updates its earthquake data within minutes of an event occurring, making it one of the most reliable sources for near real-time seismic alerts.

USGS Earthquakes MCP Server for CrewAI 3 tools — connect in under 2 minutes

Name: USGS Earthquakes
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 3 Tools Framework

Connect your CrewAI agents to USGS Earthquakes through the Vinkius — pass the Edge URL in the `mcps` parameter and every USGS Earthquakes tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="USGS Earthquakes Specialist",
    goal="Help users interact with USGS Earthquakes effectively",
    backstory=(
        "You are an expert at leveraging USGS Earthquakes tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in USGS Earthquakes "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 3 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

About USGS Earthquakes MCP Server

The USGS Earthquakes MCP Server brings planet-scale telemetry directly to your AI agent. Pulling strictly real-time and historical data from the United States Geological Survey (USGS) API, this tool gives you instant visibility into everything from micro-tremors to catastrophic seismic events globally.

When paired with CrewAI, USGS Earthquakes becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call USGS Earthquakes tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

Core Capabilities

Global Seismic Monitoring — Query real-time data across the planet.
Radial & Bounding Box Search — Focus searches on specific fault lines, continents, or specific radial points like Tokyo or San Francisco.
Magnitude & Time Filters — Zero in on data by slicing through specific date ranges and Richter thresholds.
High-Alert Diagnostics — Detect immediate tsunami warnings and review detailed human-curated significance ratings.

Whether you are building environmental response bots or running historical data analytics on tectonic shifts, this zero-auth integration puts the pulse of the planet in your hands.

The USGS Earthquakes MCP Server exposes 3 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect USGS Earthquakes to CrewAI via MCP

Follow these steps to integrate the USGS Earthquakes MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 3 tools from USGS Earthquakes

Why Use CrewAI with the USGS Earthquakes MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with USGS Earthquakes through the Model Context Protocol.

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 the 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

USGS Earthquakes + CrewAI Use Cases

Practical scenarios where CrewAI combined with the USGS Earthquakes MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries USGS Earthquakes for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries USGS Earthquakes, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain USGS Earthquakes tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries USGS Earthquakes against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

USGS Earthquakes MCP Tools for CrewAI (3)

These 3 tools become available when you connect USGS Earthquakes to CrewAI via MCP:

count_earthquakes

Get the total count of earthquakes matching specific criteria

get_significant_30_days

No parameters needed. Get highly significant global earthquakes from the last 30 days

query_earthquakes

Use parameters like starttime, endtime, minmagnitude, and geographic boundaries (latitude/longitude/maxradiuskm) to narrow the search. Maximum 20,000 events returned per query. Search for global earthquakes using USGS real-time seismic data

Example Prompts for USGS Earthquakes in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with USGS Earthquakes immediately.

"Show me the most significant earthquakes in the world from the last 30 days."

"Count the number of earthquakes above magnitude 2.5 in California in 2023."

"Check if there are any current tsunami warnings globally."

Troubleshooting USGS Earthquakes MCP Server with CrewAI

Common issues when connecting USGS Earthquakes to CrewAI through the Vinkius, and how to resolve them.

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

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

USGS Earthquakes + CrewAI FAQ

Common questions about integrating USGS Earthquakes MCP Server with CrewAI.

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.