_ registry / mcp streamable-http · checked 1h ago

DMAP-AI

https://droughtanalysis.com

Registry code: 901edf0a06be1008

api record

DMAP-AI provides historical meteorological drought analysis for a user-selected

location and period using the Standardized Precipitation Index (SPI) and wavelet

endpoint
https://droughtanalysis.com/mcp/
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is DMAP-AI live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is DMAP-AI free to use?
Yes — the hub reached it with no key and no payment.
What tools does DMAP-AI have?
5 tools: run_drought_severity_events, run_wavelet_scalogram, run_drought_periodicity_analysis, run_spi_table, debug_ping.
Is DMAP-AI safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99.6%· all time 99.6%

latency
319ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 526 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
weather & environment climate & air
used for
  • compute historical spi drought table
  • find drought events and severity
  • run wavelet analysis of drought periodicity
takes → gives
data → data, images
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • debug_ping reads open 4h ago

    Simple DMAP-AI production connector test. Use this to confirm ChatGPT is connected to the current selected-output MCP server.

    mcp-tool

    {
  "type": "object",
  "title": "debug_pingArguments",
  "properties": {}
}
    arguments 5 lines
  • run_drought_severity_events reads unknown never probed

    Use this tool whenever the user asks for drought severity analysis, drought events, a severity table, duration, minimum SPI, magnitude, or an SPI threshold such as SPI <= -0.99. This tool returns the final website-style drought events table only. It intentionally does not return the full SPI table, so ChatGPT must not recalculate the event table. Copula is not used.

    mcp-tool

    {
  "type": "object",
  "title": "run_drought_severity_eventsArguments",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "step": {
      "type": "string",
      "title": "Step",
      "default": "yearly"
    },
    "end_date": {
      "type": "string",
      "title": "End Date",
      "default": "2024-12-31"
    },
    "latitude": {
      "type": "number",
      "title": "Latitude"
    },
    "longitude": {
      "type": "number",
      "title": "Longitude"
    },
    "spi_scale": {
      "type": "integer",
      "title": "Spi Scale",
      "default": 12
    },
    "start_date": {
      "type": "string",
      "title": "Start Date",
      "default": "1981-01-01"
    },
    "data_source": {
      "type": "string",
      "title": "Data Source",
      "default": "nasa_power"
    },
    "baseline_end": {
      "type": "integer",
      "title": "Baseline End",
      "default": 2024
    },
    "yearly_method": {
      "type": "string",
      "title": "Yearly Method",
      "default": "jan_dec_totals"
    },
    "baseline_start": {
      "type": "integer",
      "title": "Baseline Start",
      "default": 1981
    },
    "category_scheme": {
      "type": "string",
      "title": "Category Scheme",
      "default": "classic_spi"
    },
    "severity_threshold": {
      "type": "string",
      "title": "Severity Threshold",
      "default": "-0.99"
    }
  }
}
    arguments 68 lines
  • run_wavelet_scalogram reads unknown never probed

    Use this tool when the user asks for the wavelet scalogram, scalogram heatmap, time-period wavelet power matrix, or high-power zones. This tool returns only a compact/downsampled scalogram result. It does not return the SPI table, drought severity event table, Copula output, or full raw backend matrix.

    mcp-tool

    {
  "type": "object",
  "title": "run_wavelet_scalogramArguments",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "step": {
      "type": "string",
      "title": "Step",
      "default": "yearly"
    },
    "end_date": {
      "type": "string",
      "title": "End Date",
      "default": "2024-12-31"
    },
    "latitude": {
      "type": "number",
      "title": "Latitude"
    },
    "longitude": {
      "type": "number",
      "title": "Longitude"
    },
    "max_times": {
      "type": "integer",
      "title": "Max Times",
      "default": 60
    },
    "spi_scale": {
      "type": "integer",
      "title": "Spi Scale",
      "default": 12
    },
    "start_date": {
      "type": "string",
      "title": "Start Date",
      "default": "1981-01-01"
    },
    "data_source": {
      "type": "string",
      "title": "Data Source",
      "default": "nasa_power"
    },
    "max_periods": {
      "type": "integer",
      "title": "Max Periods",
      "default": 24
    },
    "baseline_end": {
      "type": "integer",
      "title": "Baseline End",
      "default": 2024
    },
    "yearly_method": {
      "type": "string",
      "title": "Yearly Method",
      "default": "jan_dec_totals"
    },
    "baseline_start": {
      "type": "integer",
      "title": "Baseline Start",
      "default": 1981
    }
  }
}
    arguments 68 lines
  • run_drought_periodicity_analysis reads unknown never probed

    Use this tool when the user asks for drought periodicity, drought cycles, dominant periods, secondary periods, global wavelet spectrum, or periodicities. This tool returns only the global wavelet spectrum and ranked periodicities. It does not return the scalogram, SPI table, drought severity event table, or Copula output.

    mcp-tool

    {
  "type": "object",
  "title": "run_drought_periodicity_analysisArguments",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "step": {
      "type": "string",
      "title": "Step",
      "default": "yearly"
    },
    "end_date": {
      "type": "string",
      "title": "End Date",
      "default": "2024-12-31"
    },
    "latitude": {
      "type": "number",
      "title": "Latitude"
    },
    "longitude": {
      "type": "number",
      "title": "Longitude"
    },
    "spi_scale": {
      "type": "integer",
      "title": "Spi Scale",
      "default": 12
    },
    "start_date": {
      "type": "string",
      "title": "Start Date",
      "default": "1981-01-01"
    },
    "data_source": {
      "type": "string",
      "title": "Data Source",
      "default": "nasa_power"
    },
    "baseline_end": {
      "type": "integer",
      "title": "Baseline End",
      "default": 2024
    },
    "yearly_method": {
      "type": "string",
      "title": "Yearly Method",
      "default": "jan_dec_totals"
    },
    "baseline_start": {
      "type": "integer",
      "title": "Baseline Start",
      "default": 1981
    }
  }
}
    arguments 58 lines
  • run_spi_table reads unknown never probed

    Calculate and return a historical Standardized Precipitation Index (SPI) table for a selected location and period using ERA5 or NASA POWER precipitation data. Use this tool when the user asks for: - historical SPI values or an SPI time series; - precipitation and SPI rows for a selected location and period; - SPI drought and wetness categories; - Classic SPI threshold categories; - USDM-style category ranges applied to SPI values; - percentile-based SPI categories; - the k-means category grouping supported by DMAP-AI. This tool returns the SPI table and related table metadata only. Do not use this tool to: - identify consecutive drought events, event duration, event magnitude, or minimum SPI; use the drought-severity-events tool for those requests; - calculate SPEI; - assess soil moisture, crop yield loss, agricultural impact, hydrological impact, ecological impact, or economic damage; - produce a wavelet scalogram or drought-periodicity analysis; - provide weather forecasts, seasonal forecasts, climate projections, or future drought forecasts. Results depend on the selected dataset, baseline period, SPI accumulation scale, temporal aggregation, and available historical record. Do not describe SPI categories as direct measurements of real-world drought impacts.

    mcp-tool

    {
  "type": "object",
  "title": "run_spi_tableArguments",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "step": {
      "type": "string",
      "title": "Step",
      "default": "yearly"
    },
    "end_date": {
      "type": "string",
      "title": "End Date",
      "default": "2024-12-31"
    },
    "latitude": {
      "type": "number",
      "title": "Latitude"
    },
    "max_rows": {
      "type": "integer",
      "title": "Max Rows",
      "default": 1000
    },
    "longitude": {
      "type": "number",
      "title": "Longitude"
    },
    "spi_scale": {
      "type": "integer",
      "title": "Spi Scale",
      "default": 12
    },
    "start_date": {
      "type": "string",
      "title": "Start Date",
      "default": "1981-01-01"
    },
    "data_source": {
      "type": "string",
      "title": "Data Source",
      "default": "nasa_power"
    },
    "baseline_end": {
      "type": "integer",
      "title": "Baseline End",
      "default": 2024
    },
    "yearly_method": {
      "type": "string",
      "title": "Yearly Method",
      "default": "jan_dec_totals"
    },
    "baseline_start": {
      "type": "integer",
      "title": "Baseline Start",
      "default": 1981
    },
    "category_scheme": {
      "type": "string",
      "title": "Category Scheme",
      "default": "classic_spi"
    }
  }
}
    arguments 68 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 901edf0a06be1008.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/901edf0a06be1008/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/901edf0a06be1008/badge.svg)](https://brick.blue/agent/901edf0a06be1008?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.