Is the Olyport Fema MCP server down?

mcp-registry/com.olyport/fema · v1.26.0

healthy
Last checked 2026-10-17 22:55 UTC · handshake 6ms

As of 2026-10-17 22:55 UTC, the Olyport Fema 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,643
outages (90d)
0
tools
5

Federal disaster declarations, emergencies, and assistance data

Install Olyport Fema MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "olyport-fema-mcp-server": {
      "type": "http",
      "url": "https://mcp.olyport.com/fema/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 5 tool(s); ~1,058 tokens of tool definitions.
Scores higher than 14% of 15,327 MCP servers Glimind has audited.
Its tool list costs an agent ~1,058 tokens per session — more than 25% of servers.
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (2)

13 parameter(s) across 5 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.

Tools: get_disaster_declarations, get_disaster_detail, get_hazard_mitigation_grants, get_individual_assistance, get_public_assistance

5 of 5 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.

Tools: get_disaster_declarations, get_disaster_detail, get_hazard_mitigation_grants, get_individual_assistance, get_public_assistance

Auto-fix: 5 corrected tool definitions

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

get_disaster_declarations 1 change
{
  "name": "get_disaster_declarations",
  "description": "Get FEMA disaster declarations filtered by state, year, or type.\n\n    Returns federal disaster declarations including major disasters,\n    emergencies, and fire management assistance. Each record includes\n    the disaster number, title, declaration date, and affected area.\n\n    Args:\n        state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'FL').\n        year: Filter by fiscal year of the declaration (e.g. 2023).\n        disaster_type: Declaration type code: 'DR' (major disaster),\n     ",
  "inputSchema": {
    "type": "object",
    "title": "get_disaster_declarationsArguments",
    "properties": {
      "year": {
        "type": "integer",
        "title": "Year",
        "default": null
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 25
      },
      "state": {
        "type": "string",
        "title": "State",
        "default": null
      },
      "disaster_type": {
        "type": "string",
        "title": "Disaster Type",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_disaster_detail 1 change
{
  "name": "get_disaster_detail",
  "description": "Get detailed information about a specific FEMA disaster declaration.\n\n    Returns comprehensive data for a single disaster including all declared\n    programs, incident dates, and affected areas. Use disaster numbers\n    from get_disaster_declarations results.\n\n    Args:\n        disaster_number: The FEMA disaster number (e.g. 4737, 3604).\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_disaster_detailArguments",
    "required": [
      "disaster_number"
    ],
    "properties": {
      "disaster_number": {
        "type": "integer",
        "title": "Disaster Number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_hazard_mitigation_grants 1 change
{
  "name": "get_hazard_mitigation_grants",
  "description": "Get FEMA Hazard Mitigation Grant Program (HMGP) data.\n\n    Returns data on grants awarded to reduce future disaster losses through\n    mitigation projects such as property acquisition, elevation, and\n    infrastructure improvements.\n\n    Args:\n        state: Two-letter US state abbreviation (e.g. 'CA', 'TX').\n        limit: Maximum number of records to return (default 25, max 1000).\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_hazard_mitigation_grantsArguments",
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 25
      },
      "state": {
        "type": "string",
        "title": "State",
        "default": null
      }
    }
  },
  "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/fema"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.olyport/fema"}) 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%2Ffema.svg)](https://glimind.com/server/mcp-registry%2Fcom.olyport%2Ffema?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.olyport%2Ffema?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Ffema.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Ffema.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.olyport%2Ffema?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:52eb13b9fe6e9be5…, first seen 2026-10-17, included at leaf 5711 of 18,998. Version history · verify what your client received.

Tools (5)

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 Fema MCP server down right now?

As of 2026-10-17 22:55 UTC, the Olyport Fema 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 Fema MCP server provide?

Olyport Fema MCP server advertises 5 tools, including get_disaster_declarations, get_disaster_detail, get_hazard_mitigation_grants, get_individual_assistance, get_public_assistance.

How do I install Olyport Fema MCP server?

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

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

Glimind scanned all 5 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 Fema 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.