Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@perilpulse what's the flood and wildfire risk for 123 Main St, Austin, TX 78701?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PerilPulse MCP — per-property multi-peril risk scores (perilpulse.com)
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
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: DeepMap AI 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 1576+ 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":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"perilpulse": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-perilpulse"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-perilpulseIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
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
This server cannot be deployed
Flood, wildfire, earthquake, and coastal-storm hazard lookup for a US property.
US property risk data for agents: flood, hazards, taxes, air quality. Credits or USDC.
Zoning, ADU eligibility, flood zone, setbacks, and buildability intelligence for U.S. parcels.
Weather, climate, terrain, fire and flood risk data for any point or polygon on Earth. Free tier.
