Is the Olyport Nws Alerts MCP server down?

mcp-registry/com.olyport/nws-alerts · v1.26.0

healthy
Last checked 2026-10-18 15:52 UTC · handshake 183ms

As of 2026-10-18 15:52 UTC, the Olyport Nws Alerts MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,722
outages (90d)
0
tools
3

Active weather alerts and warnings from the National Weather Service

Install Olyport Nws Alerts MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http olyport-nws-alerts-mcp-server https://mcp.olyport.com/nws-alerts/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "olyport-nws-alerts-mcp-server": {
      "type": "http",
      "url": "https://mcp.olyport.com/nws-alerts/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 2 warning(s) across 3 tool(s); ~556 tokens of tool definitions.
Scores higher than 14% of 15,375 MCP servers Glimind has audited.
Its tool list costs an agent ~556 tokens per session — lighter than 90% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (2)

7 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_alert_detail, get_alerts, get_forecast

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_alert_detail, get_alerts, get_forecast

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.olyport%2Fnws-alerts/fixes

get_alert_detail 1 change
{
  "name": "get_alert_detail",
  "description": "Get full details of a specific NWS weather alert by its ID.\n\n    Returns the complete alert including description, instructions, and\n    affected areas. Use alert IDs from get_alerts results.\n\n    Args:\n        alert_id: The full NWS alert ID (e.g. 'urn:oid:2.49.0.1.840.0.xxx').\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_alert_detailArguments",
    "required": [
      "alert_id"
    ],
    "properties": {
      "alert_id": {
        "type": "string",
        "title": "Alert Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_alerts 1 change
{
  "name": "get_alerts",
  "description": "Get active NWS weather alerts for a US state.\n\n    Returns current weather alerts including watches, warnings, and advisories\n    issued by the National Weather Service.\n\n    Args:\n        state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'NY').\n        severity: Filter by severity level: 'Extreme', 'Severe', 'Moderate', or 'Minor'.\n        event: Filter by event type (e.g. 'Tornado Warning', 'Flash Flood Watch').\n        limit: Maximum number of alerts to return (default 25, max 500).\n ",
  "inputSchema": {
    "type": "object",
    "title": "get_alertsArguments",
    "required": [
      "state"
    ],
    "properties": {
      "event": {
        "type": "string",
        "title": "Event",
        "default": null
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 25
      },
      "state": {
        "type": "string",
        "title": "State"
      },
      "severity": {
        "type": "string",
        "title": "Severity",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_forecast 1 change
{
  "name": "get_forecast",
  "description": "Get the weather forecast for a specific latitude/longitude location.\n\n    Returns a multi-day forecast from the National Weather Service. Works for\n    any location within the United States and its territories.\n\n    Args:\n        latitude: Latitude of the location (e.g. 38.8894 for Washington DC).\n        longitude: Longitude of the location (e.g. -77.0352 for Washington DC).\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_forecastArguments",
    "required": [
      "latitude",
      "longitude"
    ],
    "properties": {
      "latitude": {
        "type": "number",
        "title": "Latitude"
      },
      "longitude": {
        "type": "number",
        "title": "Longitude"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.olyport/nws-alerts"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.olyport/nws-alerts"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fnws-alerts.svg)](https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fnws-alerts?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fnws-alerts?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fnws-alerts.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fnws-alerts.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fnws-alerts?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:10a3d201b2b4a448…, first seen 2026-10-17, included at leaf 12133 of 22,592. Version history · verify what your client received.

Tools (3)

Compare: most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Olyport Nws Alerts MCP server down right now?

As of 2026-10-18 15:52 UTC, the Olyport Nws Alerts MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Olyport Nws Alerts MCP server provide?

Olyport Nws Alerts MCP server advertises 3 tools, including get_alert_detail, get_alerts, get_forecast.

How do I install Olyport Nws Alerts MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/nws-alerts/mcp

Is the Olyport Nws Alerts MCP server safe to connect to an AI agent?

Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Olyport Nws Alerts MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.