This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
PerilPulse MCP — per-property multi-peril risk scores (perilpulse.com)
Part of Pipeworx — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tool | Description |
| Multi-peril risk scores (flood, wildfire, wind, hail, crime…) for a property address. Returns A–F grades / 0–100 scores across 25+ hazard types (flood, wildfire, earthquake, wind, hail, tornado, lightning, storm surge, crime, sinkhole, and more) — HazardHub-style property risk for insurance underwriting & due diligence. Example: perilpulse_risk({ street: "123 Main St", city: "Austin", state: "TX", zip: "78701", _apiKey: "your-key" }) |
Related MCP server: RMS Location Intelligence MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"perilpulse": {
"url": "https://gateway.pipeworx.io/perilpulse/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/perilpulse/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1867+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/perilpulse_risk. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-perilpulse is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/perilpulse/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"perilpulse": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-perilpulse"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Perilpulse data" })The gateway picks the right tool and fills the arguments automatically.
MIT
Flood, wildfire, earthquake, and coastal-storm hazard lookup for a US property.
Flood, wildfire, soils, terrain, power grid, utilities and parcels for any US location, sourced.
US property risk data for agents: flood, hazards, taxes, air quality. Credits or USDC.
Climate and disaster risk for any place or property: flood risk, heat waves, storms and hurricanes, wildfires, earthquakes, sea level rise and 7-day weather risk. Is it safe to go there? Ask about any city, address or coordinates and get this week's weather risk (heat, cold, wind, heavy rain, snow), wildfires, earthquakes, floods and cyclones happening nearby right now, long-term exposure to 2050 and 2080 (flood depth, sea level rise, extreme heat, drought, water stress) and the country's disaster-risk profile and rank among 194 countries. Also compares and ranks countries by risk for ESG and insurance research, and in Claude and other MCP Apps hosts shows an interactive map of the place right in the chat. Every value cites its source: INFORM, ND-GAIN, World Bank, CMIP6, ERA5, IPCC AR6, WRI Aqueduct, GDACS, NASA FIRMS, OpenAQ, ECCC GDPS. Remote, free, no API key, read-only.
