io.github.lostnumber07/shearline

shearline

Analyst-grade US severe weather: warnings, SPC outlooks, RAP environment, MRMS, GLM lightning

10 tools GitHub PyPI

No known CVEs

No license

Actively maintained

Last commit 14d ago

Works with most clients

Transport: stdio, http

10 tools · ~1.4k tok

Grade B · 0.7% of 200K ctx

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-lostnumber07-shearline": {
      "args": [
        "shearline"
      ],
      "command": "uvx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-lostnumber07-shearline)](https://mcppedia.org/s/io-github-lostnumber07-shearline)

Read me

What io.github.lostnumber07/shearline does

The severe-weather analyst your agent doesn't have. SHEARLINE is a free, MIT-licensed MCP server that gives AI agents analyst-grade US severe-weather tools: live warning polygons with Impact-Based Warning tags, SPC convective outlooks, RAP-derived point environments (CAPE/shear/SRH/STP computed with MetPy), MRMS radar-derived hail and rotation products, ground-truth storm reports, and a composite threat brief that synthesizes all of it. A dozen weather MCPs already wrap the basic forecast API; S

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

uvx 'shearline' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

81/100across 5 weighted dimensions

How we score →

0255075100

−19

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked shearline against OSV.dev.

Inventory

Tools (10)

Click any tool to inspect its schema.

~1.4k tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.lostnumber07/shearline safe to use?: io.github.lostnumber07/shearline has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.lostnumber07/shearline?: io.github.lostnumber07/shearline supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.lostnumber07/shearline do?: io.github.lostnumber07/shearline provides 10 tools: get_active_warnings, get_spc_outlook, get_point_environment, get_environment_trend, get_mrms_severe and 5 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.lostnumber07/shearline?: io.github.lostnumber07/shearline is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is io.github.lostnumber07/shearline actively maintained?: io.github.lostnumber07/shearline is actively maintained — last commit was 14 days ago.

Similar servers

Others in other

View all →

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

55.0k 3

Pi Lean Ctx95

Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.

3.0k 6

Trvl Mcp92

AI travel agent — 1 smart MCP tool plus 62 compatibility aliases for flights, hotels, ground transport, price alerts. No API keys required.

43 1

io.github.levnikolaevich/hex-research-mcp92

Research graph MCP for hypotheses, goals, runs, source quality, audits, and generated maps.

506 4

MCP Security Weekly

Get CVE alerts and security updates for io.github.lostnumber07/shearline and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

SHEARLINE

The severe-weather analyst your agent doesn't have. SHEARLINE is a free, MIT-licensed MCP server that gives AI agents analyst-grade US severe-weather tools: live warning polygons with Impact-Based Warning tags, SPC convective outlooks, RAP-derived point environments and forecast trends (CAPE/shear/SRH/STP computed with MetPy), MRMS radar-derived hail and rotation products, GOES lightning, ground-truth storm reports (real-time and historical), and a composite threat brief that synthesizes all of it. A dozen weather MCPs already wrap the basic forecast API; SHEARLINE deliberately skips everything they do and ships only what requires radar meteorology to expose correctly.

Informational only. Not a substitute for official NWS warnings. Every tool repeats this, because it matters: when weather threatens, follow official warnings from weather.gov and local authorities.

Tools

Tool	What it returns
`get_active_warnings(lat, lon, radius_km=40)`	Active tornado/severe-thunderstorm/flash-flood warning polygons with IBW tags (max hail size, max gust, tornado detection/damage threat), parsed storm motion, expirations, and whether the exact point is inside a polygon. Watches listed separately.
`get_spc_outlook(lat, lon, day=1)`	SPC categorical risk (TSTM→HIGH) at the point plus tornado/hail/wind probabilities and significant-severe flags, days 1–3, with interpretation calibrated to the category.
`get_point_environment(lat, lon)`	Latest RAP 13-km analysis profile computed with MetPy: MLCAPE/MUCAPE/CINs, LCL, 0–1/0–6 km shear, 0–1/0–3 km SRH, Bunkers motion, effective inflow layer, effective SRH/shear, SCP, and significant-tornado parameter — interpreted like an analyst (pulse vs. cool-season high-shear vs. classic supercell parameter space).
`get_environment_trend(lat, lon)`	The anticipatory view: a short RAP forecast series (f00/f01/f03/f06, one consistent cycle) of MLCAPE, 0–6 km shear, 0–1 km SRH, SCP and STP, with an interpretation of the trajectory (intensifying / stabilizing / steady) — for "is this getting worse" rather than "what is it now."
`get_mrms_severe(lat, lon, radius_km=40)`	MRMS maxima within radius: 60-min MESH (hail, inches and mm), low-level and mid-level rotation tracks (azimuthal shear), VIL, composite reflectivity — each with valid time and distance/bearing of the max.
`get_storm_reports(lat, lon, radius_km=80, hours=6)`	Normalized Local Storm Reports: type, magnitude with units, time, location, distance/bearing, remarks.
`get_lightning(lat, lon, radius_km=40, minutes=15)`	GOES-East GLM total-lightning activity in the recent window: flash count and rate, nearest strike (distance/bearing/time), and a tiered outdoor-safety interpretation (overhead / within-striking-distance / in-the-area).
`get_historical_storm_reports(lat, lon, date, radius_km=80)`	What hail/wind/tornado hit a point on a specific past date (`YYYY-MM-DD`, UTC) — normalized reports with magnitude+units and distance/bearing, for the insurance / ag / forensic use case. Coverage from ~2005; preliminary LSRs, not the final NCEI record.
`get_threat_brief(lat, lon)`	The showpiece: runs everything above concurrently and synthesizes a threat level (none/marginal/elevated/significant/extreme) with stated logic, haz

Tool

What it returns

get_active_warnings(lat, lon, radius_km=40)

Active tornado/severe-thunderstorm/flash-flood warning polygons with IBW tags (max hail size, max gust, tornado detection/damage threat), parsed storm motion, expirations, and whether the exact point is inside a polygon. Watches listed separately.

get_spc_outlook(lat, lon, day=1)

SPC categorical risk (TSTM→HIGH) at the point plus tornado/hail/wind probabilities and significant-severe flags, days 1–3, with interpretation calibrated to the category.

get_point_environment(lat, lon)

Latest RAP 13-km analysis profile computed with MetPy: MLCAPE/MUCAPE/CINs, LCL, 0–1/0–6 km shear, 0–1/0–3 km SRH, Bunkers motion, effective inflow layer, effective SRH/shear, SCP, and significant-tornado parameter — interpreted like an analyst (pulse vs. cool-season high-shear vs. classic supercell parameter space).

get_environment_trend(lat, lon)

The anticipatory view: a short RAP forecast series (f00/f01/f03/f06, one consistent cycle) of MLCAPE, 0–6 km shear, 0–1 km SRH, SCP and STP, with an interpretation of the trajectory (intensifying / stabilizing / steady) — for "is this getting worse" rather than "what is it now."

get_mrms_severe(lat, lon, radius_km=40)

MRMS maxima within radius: 60-min MESH (hail, inches and mm), low-level and mid-level rotation tracks (azimuthal shear), VIL, composite reflectivity — each with valid time and distance/bearing of the max.

get_storm_reports(lat, lon, radius_km=80, hours=6)

Normalized Local Storm Reports: type, magnitude with units, time, location, distance/bearing, remarks.

get_lightning(lat, lon, radius_km=40, minutes=15)

GOES-East GLM total-lightning activity in the recent window: flash count and rate, nearest strike (distance/bearing/time), and a tiered outdoor-safety interpretation (overhead / within-striking-distance / in-the-area).

get_historical_storm_reports(lat, lon, date, radius_km=80)

What hail/wind/tornado hit a point on a specific past date (YYYY-MM-DD, UTC) — normalized reports with magnitude+units and distance/bearing, for the insurance / ag / forensic use case. Coverage from ~2005; preliminary LSRs, not the final NCEI record.

get_threat_brief(lat, lon)

The showpiece: runs everything above concurrently and synthesizes a threat level (none/marginal/elevated/significant/extreme) with stated logic, haz

Frequently Asked Questions

Is io.github.lostnumber07/shearline safe to use?

io.github.lostnumber07/shearline has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.lostnumber07/shearline?

io.github.lostnumber07/shearline supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.lostnumber07/shearline do?

io.github.lostnumber07/shearline provides 10 tools: get_active_warnings, get_spc_outlook, get_point_environment, get_environment_trend, get_mrms_severe and 5 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.lostnumber07/shearline?

io.github.lostnumber07/shearline is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.

Is io.github.lostnumber07/shearline actively maintained?

io.github.lostnumber07/shearline is actively maintained — last commit was 14 days ago.

SHEARLINE

Tools

Tool	What it returns
`get_active_warnings(lat, lon, radius_km=40)`	Active tornado/severe-thunderstorm/flash-flood warning polygons with IBW tags (max hail size, max gust, tornado detection/damage threat), parsed storm motion, expirations, and whether the exact point is inside a polygon. Watches listed separately.
`get_spc_outlook(lat, lon, day=1)`	SPC categorical risk (TSTM→HIGH) at the point plus tornado/hail/wind probabilities and significant-severe flags, days 1–3, with interpretation calibrated to the category.
`get_point_environment(lat, lon)`	Latest RAP 13-km analysis profile computed with MetPy: MLCAPE/MUCAPE/CINs, LCL, 0–1/0–6 km shear, 0–1/0–3 km SRH, Bunkers motion, effective inflow layer, effective SRH/shear, SCP, and significant-tornado parameter — interpreted like an analyst (pulse vs. cool-season high-shear vs. classic supercell parameter space).
`get_environment_trend(lat, lon)`	The anticipatory view: a short RAP forecast series (f00/f01/f03/f06, one consistent cycle) of MLCAPE, 0–6 km shear, 0–1 km SRH, SCP and STP, with an interpretation of the trajectory (intensifying / stabilizing / steady) — for "is this getting worse" rather than "what is it now."
`get_mrms_severe(lat, lon, radius_km=40)`	MRMS maxima within radius: 60-min MESH (hail, inches and mm), low-level and mid-level rotation tracks (azimuthal shear), VIL, composite reflectivity — each with valid time and distance/bearing of the max.
`get_storm_reports(lat, lon, radius_km=80, hours=6)`	Normalized Local Storm Reports: type, magnitude with units, time, location, distance/bearing, remarks.
`get_lightning(lat, lon, radius_km=40, minutes=15)`	GOES-East GLM total-lightning activity in the recent window: flash count and rate, nearest strike (distance/bearing/time), and a tiered outdoor-safety interpretation (overhead / within-striking-distance / in-the-area).
`get_historical_storm_reports(lat, lon, date, radius_km=80)`	What hail/wind/tornado hit a point on a specific past date (`YYYY-MM-DD`, UTC) — normalized reports with magnitude+units and distance/bearing, for the insurance / ag / forensic use case. Coverage from ~2005; preliminary LSRs, not the final NCEI record.
`get_threat_brief(lat, lon)`	The showpiece: runs everything above concurrently and synthesizes a threat level (none/marginal/elevated/significant/extreme) with stated logic, haz

Tool

What it returns

get_active_warnings(lat, lon, radius_km=40)

get_spc_outlook(lat, lon, day=1)

SPC categorical risk (TSTM→HIGH) at the point plus tornado/hail/wind probabilities and significant-severe flags, days 1–3, with interpretation calibrated to the category.

get_point_environment(lat, lon)

get_environment_trend(lat, lon)

get_mrms_severe(lat, lon, radius_km=40)

get_storm_reports(lat, lon, radius_km=80, hours=6)

Normalized Local Storm Reports: type, magnitude with units, time, location, distance/bearing, remarks.

get_lightning(lat, lon, radius_km=40, minutes=15)

get_historical_storm_reports(lat, lon, date, radius_km=80)

get_threat_brief(lat, lon)

The showpiece: runs everything above concurrently and synthesizes a threat level (none/marginal/elevated/significant/extreme) with stated logic, haz