[Integrations](https://spiral.ai/integrations) › [opencode](https://spiral.ai/integrations/opencode) › [GDACS disaster catalogue status](https://spiral.ai/integrations/opencode/gdacs-disaster-catalogue-status)

# How to Use GDACS disaster catalogue status in opencode

Returns source status and event-count information for a selected year. Use it before an archive collection to understand the expected volume and check whether the catalogue has changed.

|  |  |
| --- | --- |
| Model | GDACS disaster catalogue status |
| Available through | Alexandria |
| Category | Public Records |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with GDACS disaster catalogue status in opencode

- Use GDACS disaster catalogue status for 2025 and show the returned annual count information in our project's archive import preview.
- Use GDACS disaster catalogue status to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from GDACS disaster catalogue status and tell me what changed since last week.
- Check GDACS disaster catalogue status and summarize what you find in three bullet points.
- Pull the newest data from GDACS disaster catalogue status and give me the result as a table.

## How to set up GDACS disaster catalogue status in opencode

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add the server**: Leave out `--global` to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.

```bash
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
```

2. **Sign in**: Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, `/mcps` starts the same sign-in.

```bash
opencode mcp auth spiral
```

3. **Check it**: Spiral shows as connected.

```bash
opencode mcp list
```

### Use the Spiral skill

1. **Send opencode this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run GDACS disaster catalogue status**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "gdacs-org/disaster-alerts/source_status",
    "input": {
      "year": 2000
    }
  }'
```

Then paste one of the prompts above: opencode finds GDACS disaster catalogue status on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/opencode

## GDACS disaster catalogue status tools and prices

- [GDACS global multi-hazard alerts · Source status](https://spiral.ai/tools/alexandria/gdacs-org/disaster-alerts/source_status) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| year | 2000 to 2100 | — | Statistic year. Default: the current year, year-to-date. |

## What can you do with GDACS disaster catalogue status in opencode?

Build a disaster event dashboard that shows GDACS assessments and available footprints alongside public infrastructure. Your coding agent can populate a historical collection, apply revisions, and add event detail views to the project.

### Maintain a disaster monitoring dashboard

Check catalogue status, collect a baseline archive, search the countries being monitored, inspect selected events, and apply subsequent changes to keep the dashboard current.

### Build a reviewed annual disaster archive

Use annual status information to plan collection, gather the year's events, search for review samples, inspect their details, and incorporate later revisions before publishing the analysis.

### Prepare recurring country briefings

Maintain a dated event collection, check source status, find relevant country alerts, examine the events behind the briefing, and update the draft when GDACS revises them.

### Review exposure around public infrastructure

Build and refresh a disaster event collection, use catalogue status to check collection scope, search relevant countries, and inspect available event footprints alongside ports, airports, or other public infrastructure.

### Compare historical event collections

Collect matching periods in different years and compare the GDACS events recorded in each. Describe the result as a comparison of GDACS records, given its stated completeness limits.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All opencode guides](https://spiral.ai/integrations/opencode)

## GDACS disaster catalogue status in other agents

- [Amp](https://spiral.ai/integrations/amp/gdacs-disaster-catalogue-status)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/gdacs-disaster-catalogue-status)
- [Claude](https://spiral.ai/integrations/claude-desktop/gdacs-disaster-catalogue-status)
- [Claude Code](https://spiral.ai/integrations/claude-code/gdacs-disaster-catalogue-status)
- [Cline](https://spiral.ai/integrations/cline/gdacs-disaster-catalogue-status)
- [Codex](https://spiral.ai/integrations/codex/gdacs-disaster-catalogue-status)
- [Cursor](https://spiral.ai/integrations/cursor/gdacs-disaster-catalogue-status)
- [Devin](https://spiral.ai/integrations/devin/gdacs-disaster-catalogue-status)
- [dots](https://spiral.ai/integrations/dots/gdacs-disaster-catalogue-status)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/gdacs-disaster-catalogue-status)
- [Gemini](https://spiral.ai/integrations/gemini/gdacs-disaster-catalogue-status)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/gdacs-disaster-catalogue-status)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/gdacs-disaster-catalogue-status)
- [goose](https://spiral.ai/integrations/goose/gdacs-disaster-catalogue-status)
- [Grok](https://spiral.ai/integrations/grok/gdacs-disaster-catalogue-status)
- [Grok Build](https://spiral.ai/integrations/grok-build/gdacs-disaster-catalogue-status)
- [Hermes](https://spiral.ai/integrations/hermes/gdacs-disaster-catalogue-status)
- [Instinct](https://spiral.ai/integrations/instinct/gdacs-disaster-catalogue-status)
- [Manus](https://spiral.ai/integrations/manus/gdacs-disaster-catalogue-status)
- [Muse](https://spiral.ai/integrations/muse/gdacs-disaster-catalogue-status)
- [Muse Code](https://spiral.ai/integrations/muse-code/gdacs-disaster-catalogue-status)
- [n8n](https://spiral.ai/integrations/n8n/gdacs-disaster-catalogue-status)
- [Notion](https://spiral.ai/integrations/notion/gdacs-disaster-catalogue-status)
- [OpenClaw](https://spiral.ai/integrations/openclaw/gdacs-disaster-catalogue-status)
- [Perplexity](https://spiral.ai/integrations/perplexity/gdacs-disaster-catalogue-status)
- [Raycast](https://spiral.ai/integrations/raycast/gdacs-disaster-catalogue-status)
- [VS Code](https://spiral.ai/integrations/vscode/gdacs-disaster-catalogue-status)
- [Windsurf](https://spiral.ai/integrations/windsurf/gdacs-disaster-catalogue-status)
- [Zapier](https://spiral.ai/integrations/zapier/gdacs-disaster-catalogue-status)

## More opencode guides

- [GDACS disaster alert search](https://spiral.ai/integrations/opencode/gdacs-disaster-alert-search)
- [GDACS disaster event archive](https://spiral.ai/integrations/opencode/gdacs-disaster-event-archive)
- [GDACS disaster alert changes](https://spiral.ai/integrations/opencode/gdacs-disaster-alert-changes)
- [GDACS disaster event details](https://spiral.ai/integrations/opencode/gdacs-disaster-event-details)
- [Federal Court of Appeal decision text](https://spiral.ai/integrations/opencode/federal-court-of-appeal-decision-text)
- [GOV.UK government organizations](https://spiral.ai/integrations/opencode/gov-uk-government-organizations)

## Questions about GDACS disaster catalogue status in opencode

**Can opencode use GDACS disaster catalogue status?**

Yes. Add Spiral to opencode as an MCP server, and opencode can find and run GDACS disaster catalogue status like any built-in tool.

**How much does GDACS disaster catalogue status cost in opencode?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your opencode plan is separate.

**Do I need an Alexandria account to use GDACS disaster catalogue status in opencode?**

No. Spiral runs GDACS disaster catalogue status on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up GDACS disaster catalogue status in opencode?**

About two minutes: add the server, then sign in, then check it.

**Does opencode wait while GDACS disaster catalogue status runs?**

GDACS disaster catalogue status runs in the background. opencode starts the run, checks on it and gives you the json when it's ready.

**Does GDACS provide confirmed disaster damage totals?**

GDACS calculates potential impact using hazard characteristics, population exposure, and vulnerability. Its terms require confirmation before notifications or automatic impact estimates are used for decisions.

**How fresh is GDACS information?**

GDACS describes its notifications as near-real-time, but explicitly gives no guarantee of completeness or timeliness. A recent retrieval does not establish that every relevant event or revision is already present.

**What does an active event mean on the GDACS homepage?**

The MHEWS homepage requires an update within the last four days, except for droughts, where the window is ten days. That label reflects recent monitoring activity rather than proof that a hazard has ended.

**Can a GDACS search return more than 100 events?**

The upstream search returns the first 100 results and supports pagination. A single result page should not be treated as the full historical collection.

**Does GDACS cover tropical cyclones outside the Atlantic?**

Yes. GDACS documents worldwide tropical cyclone coverage using NOAA and Joint Typhoon Warning Center bulletins.

