CLIO Seismic
Run earthquake-sequence analysis on saved catalogs—including completeness magnitude—from your coding agent.
Overview
io.github.iowarp/seismic-mcp is a MCP server for the Operate phase that runs earthquake-sequence analysis on saved catalogs for AI agents via stdio.
What is this MCP server?
- CLIO Seismic MCP server for earthquake-sequence analysis on saved catalogs
- Supports completeness magnitude and related catalog analytics via MCP
- clio-kit 2.2.3 on PyPI with stdio MCP transport
- Pairs with other iowarp CLIO servers for waveform and HPC workflows
- Enables agents to query and analyze seismic catalogs without custom glue scripts
- Server version 2.2.3
- Distributed as PyPI clio-kit with stdio transport
- Source at github.com/iowarp/clio-kit
Community signal: 25 GitHub stars.
What problem does it solve?
Builders with earthquake catalogs re-run the same sequence and completeness scripts by hand because agents cannot access catalog analytics natively.
Who is it for?
Solo scientific toolmakers and analysts who store earthquake catalogs locally or on cluster paths and want agent-orchestrated sequence analysis.
Skip if: App builders with no seismic catalogs, or teams needing real-time public earthquake feeds without local catalog files.
What do I get? / Deliverables
After you add seismic-mcp, your agent can invoke catalog sequence analysis—including completeness magnitude workflows—over MCP on saved data.
- MCP-accessible earthquake-sequence analysis on local catalogs
- Agent-assisted completeness magnitude and related catalog metrics
- Reduced one-off scripting for catalog iteration
Recommended MCP Servers
Journey fit
Catalog analysis on stored earthquake sequences is operational science work on persistent datasets, not initial idea validation. Iterate matches recurring catalog studies such as completeness magnitude and sequence statistics as new events arrive.
How it compares
Catalog-focused seismic analytics MCP, not a generic SQL database server or GIS map tile integration.
Common Questions / FAQ
Who is io.github.iowarp/seismic-mcp for?
It is for developers and researchers analyzing saved earthquake catalogs who want MCP-driven sequence and completeness analysis from coding agents.
When should I use io.github.iowarp/seismic-mcp?
Use it when you operate on persistent event catalogs and need repeatable completeness magnitude and sequence statistics inside agent sessions.
How do I add io.github.iowarp/seismic-mcp to my agent?
Install clio-kit from PyPI, register io.github.iowarp/seismic-mcp with stdio in your MCP client, and provide access to your saved catalog files or paths.